---
title: "Get a single mandate"
method: GET
path: "/mandates/{mandate_id}"
tags: ["Mandate"]
---

# Get a single mandate

`GET /mandates/{mandate_id}`

## Request

- Base URL: `https://api.gocardless.com`
- URL: `https://api.gocardless.com/mandates/{mandate_id}`
- Auth: HTTP bearer

Retrieves the details of an existing mandate.

## Path parameters

- `mandate_id` string, required

## Headers

- `GoCardless-Version` string, required

## Response `200`

Successful response

- MandateSingleResourceResponse
  - `mandates` Mandate: Mandates represent the Direct Debit mandate with a [customer](https://docs.gocardless.com/docs/api-reference/customer). GoCardless will notify you via a [webhook](https://docs.gocardless.com/docs/api-reference/webhooks) whenever the status of a mandate changes.
    - `id` string: Unique identifier, beginning with "MD". Note that this prefix may not apply to mandates created before 2016.
    - `created_at` string, date-time: Fixed [timestamp](https://docs.gocardless.com/docs/api-reference/data-conventions#dates-and-times), recording when this resource was created.
    - `reference` string, nullable: Unique reference. Different schemes have different length and [character set](https://docs.gocardless.com/docs/api-reference/character-sets) requirements. GoCardless will generate a unique reference satisfying the different scheme requirements if this field is left blank.
    - `status` 'pending_customer_approval' | 'pending_submission' | 'submitted' | 'active' | 'failed' | 'cancelled' | 'expired' | 'consumed' | 'blocked' | 'suspended_by_payer': One of: - `pending_customer_approval`: the mandate has not yet been signed by the second customer - `pending_submission`: the mandate has not yet been submitted to the customer's bank - `submitted`: the mandate has been submitted to the customer's bank but has not been processed yet - `active`: the mandate has been successfully set up by the customer's bank - `suspended_by_payer`: the mandate has been suspended by payer - `failed`: the mandate could not be created - `cancelled`: the mandate has been cancelled - `expired`: the mandate has expired due to dormancy - `consumed`: the mandate has been consumed and cannot be reused (note that this only applies to schemes that are per-payment authorised) - `blocked`: the mandate has been blocked and payments cannot be created
    - `scheme` string, nullable: <a name="mandates_scheme"></a>Bank payment scheme to which this mandate and associated payments are submitted. Can be supplied or automatically detected from the customer's bank account.
    - `mandate_type` 'bank_debit' | 'instant' | 'recurring' | 'vrp_commercial' | 'vrp_sweeping', nullable: Mandate type
    - `next_possible_charge_date` string, date, nullable: The earliest date that can be used as a `charge_date` on any newly created payment for this mandate. This value will change over time.
    - `next_possible_standard_ach_charge_date` string, date, nullable: If this is an ACH mandate, the earliest date that can be used as a `charge_date` on any newly created payment to be charged through standard ACH, rather than Faster ACH. This value will change over time. It is only present in the API response for ACH mandates.
    - `payments_require_approval` boolean: Boolean value showing whether payments and subscriptions under this mandate require approval via an automated email before being processed.
    - `verified_at` string, date-time, nullable: [Timestamp](https://docs.gocardless.com/docs/api-reference/data-conventions#dates-and-times) recording when this mandate was verified.
    - `metadata` CustomerMetadata: Key-value store of custom data. Up to 3 keys are permitted, with key names up to 50 characters and values up to 500 characters.
    - `links` MandateLinks
      - `customer_bank_account` string: ID of the associated [customer bank account](https://docs.gocardless.com/docs/api-reference/customer-bank-account) which the mandate is created and submits payments against.
      - `creditor` string: ID of the associated [creditor](https://docs.gocardless.com/docs/api-reference/creditor).
      - `new_mandate` string: ID of the new mandate if this mandate has been replaced.
      - `customer` string: ID of the associated [customer](https://docs.gocardless.com/docs/api-reference/customer)
    - `consent_parameters` MandateConsentParameters, nullable: (Optional) Payto and VRP Scheme specific information
      - `id` string: Unique identifier for the consent parameters
      - `scheme` string: The scheme associated with the consent parameters
      - `currency` string: The currency for the consent parameters
      - `fixed_amount_per_payment` integer, nullable: The fixed amount for each payment, in the lowest denomination for the currency
      - `max_amount_per_payment` integer, nullable: The maximum amount that can be charged for a single payment
      - `period` 'day' | 'week' | 'month' | 'year' | 'flexible': The repeating period for this mandate
      - `max_amount_per_period` integer, nullable: The maximum total amount that can be charged for all payments in this period
      - `max_payments_per_period` integer, nullable: The maximum number of payments that can be collected in this period
      - `start_date` string: The date from which payments can be taken
      - `end_date` string, nullable: The latest date at which payments can be taken, must occur after start_date if present
      - `period_alignment` 'calendar' | 'consent' | 'creation_date': The alignment of the payment period.
    - `authorisation_source` 'web' | 'telephone' | 'paper': This field is ACH specific, sometimes referred to as [SEC code](https://www.moderntreasury.com/learn/sec-codes). This is the way that the payer gives authorisation to the merchant. web: Authorisation is Internet Initiated or via Mobile Entry (maps to SEC code: WEB) telephone: Authorisation is provided orally over telephone (maps to SEC code: TEL) paper: Authorisation is provided in writing and signed, or similarly authenticated (maps to SEC code: PPD)
    - `funds_settlement` 'managed' | 'direct': This field will decide how GoCardless handles settlement of funds from the customer. - `managed` will be moved through GoCardless' account, batched, and payed out. - `direct` will be a direct transfer from the payer's account to the merchant where invoicing will be handled separately.
    - `consent_type` 'one_off' | 'single' | 'recurring' | 'standing' | 'sporadic', nullable: (Optional) Specifies the type of authorisation agreed between the payer and merchant. It can be set to one-off, recurring or standing for ACH, or single, recurring and sporadic for PAD.

## Other responses

- `400`: Bad Request
- `401`: Unauthorised
- `404`: Not found
- `422`: Validation Error
- `500`: Internal Error

---

[API](https://skmtc.dev/gocardless/apis/gocardless-api.md) - [All operations](https://skmtc.dev/gocardless/apis/gocardless-api/llms.txt) - [OpenAPI document](https://skmtc.dev/gocardless/apis/gocardless-api/revisions/4dd3dae45364?raw)