Use payment orders to send payment instructions to your partner banks, CSMs, or Swift through Mambu Payments. Mambu Payments receives payment orders, formats them, batches them if applicable, and sends them to your partner banks, CSMs, or Swift. Mambu Payments retrieves and updates payment statuses. Payment status updates are sent to your webhooks as events.

Attribute	Description
id string	The payment order ID.
object string	Always `payment_order`.
connected_account_id string	The ID of the connected account used to send the payment order.
type string	The payment scheme or network. Supported values are listed in the payment types page.
treasury_option string	The treasury payment option, when `type` = `treasury`. Supported treasury options include: - `local`, for same-country treasury payments - `international`, for cross-country treasury payments - `safeguarding`, for treasury payments between settlement and safeguarding accounts - `relocated`, to initiate payments from another bank than the connected account's bank, with whom an agreement has been signed
confidentiality_option string	Only confidentiality option supported is `payroll`.
fee_option string	Network payment fee preference. Only applicable to Swift payments (`type`=`swift`). Supported values include: - `originator`: fee paid by the originating party - `receiver`: paid by the receiving party - `shared`: fee split between the originating and the receiving party
purpose string	The purpose code of the payment, ensuring compliance with regulatory requirements of certain beneficiary countries. Only applicable to `swift` and `chaps` payment types.
category_purpose_code string	The category purpose of the payment. Recommended for `chaps` payment types.
uetr string	Unique end-to-end transaction reference. Can be used to track payments with Swift GPI.
swift_gpi object	Contains information about Swift GPI. When applicable, this object will contain the following properties: - `status`: Swift GPI status, either `created`, `in_progress`, `received`, or `rejected` - `confirmed_at`: date on which the payment has been fully confirmed - `confirmed_amount`: amount which has been settled on the receiving account - `confirmed_currency`: currency of the payment which has been settled on the receiving account - `tracking_progress`: contains Swift GPI tracking steps involved on the processing of the payment Tracking steps recorded in the `tracking_progress` attribute contain the following properties: - `id`: tracking step ID - `processed_at`: tracking step processing date - `status`: tracking step status, either executed (ACSP), received (ACCC), or rejected (RJCT) - `status_details`: tracking step status details and reason codes (for instance ACCC, AC04, G005, etc.) - `bank_code`: BIC of the bank or financial institution processing the payment - `fee_amount`: potential fee applied on the processing of the payment - `fee_currency`: currency of the potential fee applied on the processing of the payment
direction string	Either `credit` or `debit`, from the perspective of the receiving account: - A `credit` payment order credits a counterparty account and debits your account - A `debit` payment order debits a counterparty account and credits your account Combined with the payment order `type`, the `direction` indicates the payment scheme or method used. For instance: - A payment order with `type` = `sepa` and `direction` = `credit` is a SEPA credit transfer - A payment order with `type` = `bacs` and `direction` = `debit` is a Bacs direct debit
amount integer	The payment amount, in the currency's smallest unit. For instance, euro smallest unit is cents and €20 is thus represented as `2000`. See Currency codes and decimals for the number of decimals per currency.
currency string	The three-letter ISO 4217 currency code. See Currency codes and decimals for currency codes supported.
reference string	The payment reference as it will appear on the originating account and receiving account statements, with a maximum of 140 characters.
end_to_end_id string	The payment's end-to-end ID. Mambu Payments (formerly Numeral) will automatically generate one if no value was provided. Only supported for specific banks and payment schemes. Contact us to get more details about it.
originating_account object	The account originating the payment. It must only be filled when sending payments from financial institution connected accounts, and if the `originating_account_id` property is not filled. It must be left empty for corporate customers. The `originating_account` object includes the following attributes: - `account_number`: the account number of the originating account. - `account_number_format`: the account number format of the originating account. See accepted account number formats here - `bank_code`: the BIC / Swift code or sort code, depending on the country and bank. Only upper case letters allowed - `bank_code_format`: format of the bank code. See bank code formats here - `holder_name`: the name of the company or individual holding the account - `creditor_identifier`: the creditor identifier, in case of SEPA direct debit or Bacs payments - `holder_address`: the account holder address, as an address object - `organization_identification`: the account organization identification, as an organization identification object - `private_identification`: the account private identification, as a private identification object - `bank_name`: the name of the bank - `bank_address`: the bank address, as an address object
originating_account_id string	The ID of the internal account sending the payment instruction. Only applicable to financial institutions connected accounts. It must be left empty if `originating_account` is filled.
ultimate_originator object	The ultimate originator of the payment. Only applicable to payment service providers. It is composed of the following attributes: - `holder_name`: the name of the ultimate originator, either an individual or a business - `holder_address`: the address of the ultimate originator, as an address object - `organization_identification`: the account organization identification, as an organization identification object - `private_identification`: the account private identification, as a private identification object
receiving_account object	The account receiving the payment: - If `direction` = `credit`, the receiving account is the account to credit - If `direction` = `debit`, the receiving account is the account to debit It must be left empty if `receiving_account_id` is filled. The `receiving_account` object includes the following attributes: - `account_number`: the account number of the originating account. - `account_number_format`: the account number format of the originating account. See accepted account number formats here - `bank_code`: the BIC / Swift code or sort code, depending on the country and bank. Only upper case letters allowed - `bank_code_format`: format of the bank code. See bank code formats here - `holder_name`: the name of the company or individual holding the account - `holder_address`: the account holder address, as an address object - `organization_identification`: the account organization identification, as an organization identification object - `private_identification`: the account private identification, as a private identification object - `bank_name`: the name of the bank - `bank_address`: the bank address, as an address object
receiving_account_id string	The ID of the external account receiving the payment. It must be left empty if `receiving_account` is filled. When `direction` = `credit`, the receiving account is the account to credited. When `direction` = `debit`, the receiving account is the account to debit.
direct_debit_mandate object	The mandate authorizing the direct debit, only for direct debit payments. The `direct_debit_mandate` object includes the following attributes: - `reference`: the mandate reference. It will appear on the account statement of the account debited - `signature_date`: the mandate signature date - `type`: the mandate type, either `sepa_core` or `sepa_b2b` - `frequency`: the mandate sequence, either `one_off` or `recurring` - ~~`sequence`: the mandate sequence, either `one_off` or `recurring`~~ (this field has been deprecated)
direct_debit_mandate_id string	The direct debit mandate ID. It must be left empty if `direct_debit_mandate` is filled.
direct_debit_sequence_type string	The direct debit sequence, such as `first`, `recurring`, `final` or `one_off`. This field is optional by default and is only mandatory when `direct_debit_mandate` or `direct_debit_mandate_id` are provided.
value_date date	The payment order value date. It might be updated as the payment is processed by the bank or the CSM.
requested_execution_date date	The payment order requested execution date. Learn more about payment warehousing.
initiated_at datetime	The payment order initiation UTC timestamp with ISO 8601 format to the milliseconds without trailing zeros. Only supported for `sepa_instant` payments.
status string	The payment order status. It will be updated as the payment order is processed. See Payment order lifecycle for a comprehensive list of payment order statuses.
status_details string	The payment order status details.
reconciliation_status string	The payment order reconciliation status. Either `unreconciled`, `reconciled`, or `partially_reconciled`.
reconciled_amount integer	The amount reconciled, calculated as the sum of the reconciliations created for this payment order.
auto_approval boolean	When `auto_approval` = `true`, the payment order is created in status `approved`. When `auto_approval` = `false`, the payment is created in status `pending_approval` and must be approved to be sent. Set to `false` by default.
payment_validation object	Information about the payment validation, like the validation rules and validation statuses.
retry_details object	All relevant information about the payment order retries. The `retry_details` object includes the following attributes: - `payment_retry_rule_id`: the ID of the payment retry rule attached to the payment order. See Payment retry rule - `original_payment_id`: the ID of the original payment order that led to the current object through a chain of retries - `retried_from_payment_id`: the ID of the payment order the payment order has been retried from, in case the payment order is a retry - `retried_to_payment_id`: the ID of the payment order the payment order has been retried to, in case the payment order has been retried - `retry_scheduled_at`: the UTC timestamp of the expected retry
settlement_method string	Settlement method of the payment. Only filled for Swift correspondent payments. Values can be: - `instructing_agent`: when the settlement was performed by the instructing agent - `instructed_agent`: when the settlement should be done by the instructed agent - `cover`: when the settlement will be performed separately using a cover payment
intermediary_agents array	Intermediary financial institution agents via which the payment should be processed. Only applicable to `swift` payments. Intermediary agents can be composed of the following attributes: - `name`: Name of the intermediary agent - `bank_code`: Bank code of the intermediary agent - `legal_entity_identifier`: Legal entity identifier (LEI) of the intermediary agent - `other`: Other identification of the intermediary agent
previous_instructing_agents array	Previous instructing agents via which the payment went through before Mambu Payments. Only applicable to `swift` payments. Intermediary agents can be composed of the following attributes: - `name`: Name of the intermediary agent - `bank_code`: Bank code of the intermediary agent - `legal_entity_identifier`: Legal entity identifier (LEI) of the intermediary agent - `other`: Other identification of the intermediary agent
routing_instruction string	Specific instructions intended for the next financial institution in the payment chain to ensure proper processing of the transaction. Only applicable to `swift` payments.
metadata object	Additional data in JSON `key:value` format. See Metadata.
custom_fields object	Custom fields in JSON `key:value` format. See Custom fields.
bank_data object	Bank data in JSON `key:value` format. This object contains banking information managed by Mambu Payments (formerly Numeral) and determined by the specific integration rules of each bank. This includes fields such as `transaction_id` which are set according to banking protocols and cannot be set by users. Client-specific information can be stored in metadata and custom fields and will persist through the payment order processing in Mambu Payments (formerly Numeral).
cbs_data object	This object contains all relevant information about the payment in the context of the integration with Mambu Core. Learn more in our dedicated guides Mambu Deposits integration and Mambu Lending integration.
idempotency_key string	A unique key sent by the customer and used by Mambu Payments (formerly Numeral) to identify subsequent retries of the same request. See Idempotency.
created_at datetime	The UTC timestamp of the creation of the payment order.

📘
Execution date
A payment order does not have an execution date. The execution date is the date when the payment order is added to a payment file and sent to the bank, taking into consideration applicable your bank's cut-off time and CSM's calendar.
If you would like to schedule and execute a payment order on a specific date, you should create it on this date, taking into consideration applicable your bank's cut-off time and CSM's calendar.

Below are examples of payment orders:

{
   "id": "b69837bf-e784-4bd1-b0d0-2ad0e61a89b6",
   "idempotency_key": "a23a61d8-9adf-4bd2-a453-fd3938c8871f",
   "object": "payment_order",
   "connected_account_id": "254e3100-afd6-44f2-8084-87e8ae67b554",
   "type": "sepa",
   "treasury_option": null,
   "confidentiality_option": null,
   "direction": "credit",
   "amount": 2000,
   "currency": "EUR",
   "reference": "Invoice 1234",
   "purpose": null,
   "category_purpose_code": null,
   "uetr": null,
   "intermediary_agents": [],
   "routing_instruction": null,
   "originating_account": {
      "account_number": "FR7601234567890627967100010",
      "bank_code": "SOGEFRPP",
      "holder_name": "SoftwareCo",
      "creditor_identifier": "",
      "holder_address": {
         "line_1": "1, rue de l'Abondance",
         "line_2": "",
         "postal_code": "69003",
         "region_state": "",
         "city": "Lyon",
         "country": "FR"
      }
   },
   "receiving_account_id": "b38f5318-a389-4278-9cbe-d16116750982",
   "receiving_account": {
      "account_number": "FR7601234567891127967100082",
      "bank_code": "BNPAFRPPXXX",
      "holder_name": "PartnerCo",
      "holder_address": {
         "line_1": "1, rue de la Bourse",
         "line_2": "",
         "postal_code": "59000",
         "region_state": "",
         "city": "Lille",
         "country": "FR"
      }
   },
   "direct_debit_mandate": {},
   "direct_debit_mandate_id": "",
   "value_date": "2022-01-03",
   "requested_execution_date": "",
   "status": "executed",
   "status_details": "",
   "auto_approval": false,
   "approvals": [{
      "type": "api_key",
      "id": "64b251dc-abad-4ae9-8f35-8980be766cc5",
      "approved_at": "2025-09-08T09:08:24.715405993Z",
      "details": null
   }],
   "payment_validation": {
      "status": "successful",
      "validation_results": [{
         "payment_validation_rule_id": "f1613230-50d6-49cd-89d1-0f019f71f7c7",
         "status": "successful",
         "validations": [
            [{
               "type": "liquidity_screening",
               "status": "successful",
               "status_details": "balance correct",
               "resource_id": "123-ABC",
               "resource_url": "my-liquidity.com/123-ABC"
            }],
            [{
               "type": "sanctions_screening",
               "status": "successful",
               "status_details": "no match",
               "resource_id": "DEF-456",
               "resource_url": "my-sanction.com/DEF-456"
            }]
         ]
      }]
   },
   "retry_details": {
      "payment_retry_rule_id": "dec3336c-2ec6-47ee-a69f-33353c7fdfaf",
      "original_payment_id": "bf400636-dd95-426e-8a13-e9b49aa0838b",
      "retried_to_payment_id": "9dcdaab7-861c-4e3b-8101-44fef53e289f",
      "retried_from_payment_id": "e0362ec5-0292-40d9-b6ad-985528da0443",
      "retry_scheduled_at": "2022-01-03T11:53:19.734182Z"
   },
   "reconciled_amount": 2000,
   "reconciliation_status": "reconciled",
   "metadata": {},
   "custom_fields": {},
   "bank_data": {
      "file_id": "a815e756-5576-4d40-9fbd-38ec304b856c",
      "message_id": "1gXrtKMxLJ",
      "transaction_id": "1zDrzOMxCJ",
      "end_to_end_id": "c3b2d737bc"
   },
  "cbs_data": {
    "transactions": [{
			"id": "1534",
			"type": "withdrawal",
			"channel": "cash",
			"context": "deposit",
			"booked_at": "2026-03-03T13:04:12.886736405Z",
			"account_id": "JELM775",
			"external_id": "019cb3cc-3b38-7d0a-b2be-58e8aeea2486",
			"authorization_id": "bcee9199-3194-449c-bd73-750e4d3454e6"
		}],
    "loan_ids": null,
    "credit_arrangement_id": null
  },
   "created_at": "2025-01-03T11:53:19.734182Z",
   "created_by": {
      "type": "api_key",
      "id": "64b251dc-abad-4ae9-8f35-8980be766cc5"
   }
}

{
   "id": "b69837bf-e784-4bd1-b0d0-2ad0e61a89b6",
   "idempotency_key": "a23a61d8-9adf-4bd2-a453-fd3938c8871f",
   "object": "payment_order",
   "connected_account_id": "254e3100-afd6-44f2-8084-87e8ae67b554",
   "type": "sepa_instant",
   "treasury_option": null,
   "confidentiality_option": null,
   "direction": "credit",
   "amount": 2000,
   "currency": "EUR",
   "reference": "Invoice 1234",
   "purpose": null,
   "category_purpose_code": null,
   "uetr": null,
   "intermediary_agents": [],
   "routing_instruction": null,
   "originating_account": {
      "account_number": "FR7601234567890627967100010",
      "bank_code": "SOGEFRPP",
      "holder_name": "SoftwareCo",
      "creditor_identifier": "",
      "holder_address": {
         "line_1": "1, rue de l'Abondance",
         "line_2": "",
         "postal_code": "69003",
         "region_state": "",
         "city": "Lyon",
         "country": "FR"
      }
   },
   "receiving_account": {
      "account_number": "FR7601234567891127967100082",
      "bank_code": "BNPAFRPPXXX",
      "holder_name": "PartnerCo",
      "holder_address": {
         "line_1": "1, rue de la Bourse",
         "line_2": "",
         "postal_code": "59000",
         "region_state": "",
         "city": "Lille",
         "country": "FR"
      }
   },
   "direct_debit_mandate": {},
   "direct_debit_mandate_id": "",
   "retried_from_payment_id": "dec3336c-2ec6-47ee-a69f-33353c7fdfaf",
   "retried_to_payment_id": "",
   "value_date": "2022-01-03",
   "requested_execution_date": "",
   "status": "executed",
   "status_details": "",
   "auto_approval": false,
   "approvals": [{
      "type": "api_key",
      "id": "64b251dc-abad-4ae9-8f35-8980be766cc5",
      "approved_at": "2025-09-08T09:08:24.715405993Z",
      "details": null
   }],
   "payment_validation": {
      "status": "successful",
      "validation_results": [{
         "payment_validation_rule_id": "f1613230-50d6-49cd-89d1-0f019f71f7c7",
         "status": "successful",
         "validations": [
            [{
               "type": "liquidity_screening",
               "status": "successful",
               "status_details": "balance correct",
               "resource_id": "123-ABC",
               "resource_url": "my-liquidity.com/123-ABC"
            }],
            [{
               "type": "sanctions_screening",
               "status": "successful",
               "status_details": "no match",
               "resource_id": "DEF-456",
               "resource_url": "my-sanction.com/DEF-456"
            }]
         ]
      }]
   },
   "reconciled_amount": 2000,
   "reconciliation_status": "reconciled",
   "metadata": {},
   "bank_data": {
      "file_id": "a815e756-5576-4d40-9fbd-38ec304b856c",
      "message_id": "1gXrtKMxLJ",
      "transaction_id": "1zDrzOMxCJ",
      "end_to_end_id": "c3b2d737bc"
   },
   "created_at": "2025-01-03T11:53:19.734182Z",
   "created_by": {
      "type": "api_key",
      "id": "64b251dc-abad-4ae9-8f35-8980be766cc5"
   }
}

{
   "id": "b69837bf-e784-4bd1-b0d0-2ad0e61a89b6",
   "idempotency_key": "a23a61d8-9adf-4bd2-a453-fd3938c8871f",
   "object": "payment_order",
   "connected_account_id": "254e3100-afd6-44f2-8084-87e8ae67b554",
   "type": "sepa",
   "treasury_option": null,
   "confidentiality_option": null,
   "direction": "debit",
   "amount": 2000,
   "currency": "EUR",
   "reference": "Invoice 1234",
   "purpose": null,
   "category_purpose_code": null,
   "uetr": null,
   "intermediary_agents": [],
   "routing_instruction": null,
   "originating_account": {
      "account_number": "FR7601234567890627967100010",
      "bank_code": "SOGEFRPP",
      "holder_name": "SoftwareCo",
      "creditor_identifier": "FR12ZZZ123456",
      "holder_address": {
         "line_1": "1, rue de l'Abondance",
         "line_2": "",
         "postal_code": "69003",
         "region_state": "",
         "city": "Lyon",
         "country": "FR"
      }
   },
   "receiving_account": {
      "account_number": "FR7601234567891127967100082",
      "bank_code": "BNPAFRPPXXX",
      "holder_name": "PartnerCo",
      "holder_address": {
         "line_1": "1, rue de la Bourse",
         "line_2": "",
         "postal_code": "59000",
         "region_state": "",
         "city": "Lille",
         "country": "FR"
      }
   },
   "direct_debit_sequence_type": "final",
   "direct_debit_mandate": {
      "reference": "DDb05e47338e87",
      "signature_date": "2022-07-14",
      "type": "sepa_core",
      "frequency": "recurring",
      "sequence": "recurring"
   },
   "direct_debit_mandate_id": "fc57af6a-2545-11ee-be56-0242ac120002",
   "retried_from_payment_id": "dec3336c-2ec6-47ee-a69f-33353c7fdfaf",
   "retried_to_payment_id": "",
   "value_date": "2022-01-03",
   "requested_execution_date": "2022-01-03",
   "status": "executed",
   "status_details": "",
   "auto_approval": false,
   "approvals": [{
      "type": "api_key",
      "id": "64b251dc-abad-4ae9-8f35-8980be766cc5",
      "approved_at": "2025-09-08T09:08:24.715405993Z",
      "details": null
   }],
   "payment_validation": {
      "status": "successful",
      "validation_results": [{
         "payment_validation_rule_id": "f1613230-50d6-49cd-89d1-0f019f71f7c7",
         "status": "successful",
         "validations": [
            [{
               "type": "liquidity_screening",
               "status": "successful",
               "status_details": "balance correct",
               "resource_id": "123-ABC",
               "resource_url": "my-liquidity.com/123-ABC"
            }],
            [{
               "type": "sanctions_screening",
               "status": "successful",
               "status_details": "no match",
               "resource_id": "DEF-456",
               "resource_url": "my-sanction.com/DEF-456"
            }]
         ]
      }]
   },
   "reconciled_amount": 2000,
   "reconciliation_status": "reconciled",
   "metadata": {},
   "bank_data": {
      "file_id": "a815e756-5576-4d40-9fbd-38ec304b856c",
      "message_id": "1gXrtKMxLJ",
      "transaction_id": "1zDrzOMxCJ",
      "end_to_end_id": "c3b2d737bc"
   },
   "created_at": "2022-01-01T11:53:19.734182Z",
   "created_by": {
      "type": "api_key",
      "id": "64b251dc-abad-4ae9-8f35-8980be766cc5"
   }
}

Swift is a trademark of S.W.I.F.T. SC.