# Schedule a SEPA Direct Debit collection

**POST /v2/collections**

This endpoint allows you to schedule a SEPA Direct Debit collection to be credited on one of your accounts.


## Servers
- Production: https://api.memo.bank (Production)
- Sandbox: https://api.sandbox.memo.bank (Sandbox)


## Authentication methods
- Jwt


## Parameters



### Body: application/json (object)

- **amount** (integer(int64))
  Amount to be collected, in cents. The currency is always EURO.
- **mandate** (object)
  The SEPA Direct Debit collection mandate to be used.
- **scheduled_date** (string(date))
  The ISO8601 formatted date on which the direct debit collection will be submitted. This date must not be in the past. If your direct debit is scheduled to be submitted on a non-business day, it will be effectively submitted on the next business day. The execution will then happen on the following business day. For example, a direct debit scheduled on a Saturday will be submitted on the following Monday and executed on the Tuesday (assuming that both week days are business days).
- **local_iban** (string)
  Existing IBAN to be credited. It can be the main IBAN of an account or a virtual IBAN.
- **message** (string)
  Message attached to this collection, visible to all involved parties.
- **end_to_end_id** (string)
  Unique identification to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. It can be used for reconciliation or to link tasks relating to the transaction.
- **internal_note** (string)
  Internal note attached to this collection, visible only in your Memo Bank workspace.
- **custom_id** (string)
  Custom identifier that will be attached to the transaction resulting from this collection. It will not be transmitted nor visible in your Memo Bank workspace. It can only be retrieved or used to search for transactions via Memo Bank API.
- **custom_metadata** (string)
  Custom metadata that will be attached to the transaction resulting from this collection. It will not be transmitted nor visible in your Memo Bank workspace and can only be retrieved via API.


## Responses
### 200
OK

#### Body: application/json (object)
- **id** (string(uuid))
  ID of the collection.
- **reference** (string(uuid))
  Unique reference, can be used to correlate with the resulting Transaction.
- **amount** (integer(int64))
  The collection amount, in cents.
- **currency** (string)
  Currency of the amount, in ISO 4217 format.
- **mandate** (object)
  The SEPA Direct Debit collection mandate used.
- **scheduled_date** (string(date))
  The collection scheduled date, in ISO8601 format.
- **local_iban** (string)
  IBAN credited or to be credited. It can be the main IBAN of an account or a virtual IBAN.
- **account_id** (string(uuid))
  ID of the account this collection belongs to, it can be missing while we process it according to the local IBAN.
- **status** (string)
  Current status of the collection.
- **failure_code** (string)
  Code that represents the failure reason when the collection has failed:
  - `invalid_mandate_iban`: The mandate's IBAN is invalid.
  - `unreachable_mandate_iban`: The mandate's IBAN is unreachable for the given scheme.
  - `missing_debtor_address`: The debtor address is missing and required for non-EEA SEPA countries.
  - `core_limit_exceeded`: The limit for CORE collections was exceeded.
  - `debtor_refusal`: The debtor has refused the collection.
  - `debtor_bank_account_closed`: The debtor's bank account is closed.
  - `debtor_bank_insufficient_funds`: The debtor's bank account has insufficient funds.
  - `debtor_bank_error`: The debtor's bank sent us an error.
  - `debtor_bank_invalid_bank_details`: The debtor's bank account does not exist or no longer exists.
  - `debtor_bank_refusal`: The debtor's bank has refused the collection.
  - `intermediary_system_error`: The interbank network sent us an error.
  - `memo_error`: Something went wrong on our side.
  - `memo_refusal`: We had to reject the collection.
  - `execution_failure`: Other or undefined pre-settlement execution failures.

  The following codes can only be present on collections initiated as part of a bulk. 
  When initiating a single collection, those codes will be returned as an error response 
  and the collection won’t be created at all:
  - `account_cannot_receive_collections`: The account cannot receive collections.
  - `current_account_not_found`: The provided local IBAN does not exist.
  - `creditor_is_saving_account`: The provided local IBAN is a Booster account.
  - `no_sepa_creditor_identifier`: You need to setup a SEPA creditor identifier with your banker.
  - `mandate_info_missing`: New mandate information must be complete.
  - `mandate_iban_mismatch`: The mandate reference already exists but with a different IBAN.
  - `collection_to_same_account`: The local IBAN and the debtor IBAN can not be the same.
- **message** (string)
  Message attached to this collection, visible to all involved parties.
- **end_to_end_id** (string)
  Unique identification to unambiguously identify the transaction. This identification is passed on, unchanged, throughout the entire end-to-end chain. It can be used for reconciliation or to link tasks relating to the transaction.
- **internal_note** (string)
  Internal note attached to this collection, visible only in your Memo Bank workspace.
- **custom_id** (string)
  Custom identifier attached to the transaction resulting from this collection. It is not transmitted nor visible in your Memo Bank workspace. It can only be retrieved or used to search for transactions via Memo Bank API.
- **custom_metadata** (string)
  Custom metadata attached to the transaction resulting from this collection. It is not transmitted nor visible in your Memo Bank workspace and can only be retrieved via API.
- **return_transaction_id** (string(uuid))
  If the collection is returned, ID of the corresponding debit transaction.


[Powered by Bump.sh](https://bump.sh)