Fiat Payments

Simulates pay-ins with different currencies and payment methods in the sandbox environment.

This version allows specifying originator entity details (individual or company) for more comprehensive testing scenarios.

Important: A 201 response indicates the pay-in was accepted for processing. It does not mean the funds have settled. The transaction may still be rejected asynchronously, for example, due to a blocked account, financial crime screening holds, or compliance checks. Monitor webhooks for the final transaction status.

post/payment/v2/payins/simulation

Request

Request body

walletIdWalletId required(unresolved $ref)
method'FASTER_PAYMENT' | 'SWIFT' | 'SEPA_CT' | 'SEPA_INST' | 'ACH' | 'ACH_SAME_DAY' | 'FEDWIRE' | 'CUBIX'

Payment method to be utilised for the pay-in. Optional. If not provided, the logic will be based on other dynamically determined attributes and routed for the specific wallet.

Use the following methods for each currency:

  • GBP: FASTER_PAYMENT

  • EUR: SEPA_CT, SEPA_INST, or SWIFT

  • USD: ACH, ACH_SAME_DAY, FEDWIRE, CUBIX, or SWIFT

remittanceInformationRemittanceInformation required(unresolved $ref)
amountnumber required

The amount of the pay-in transaction.

currencystring required

Currency code (ISO-4217 format) for the pay-in transaction.

Response

Accepted for processing. This does not indicate that the pay-in has settled. The transaction may still be rejected asynchronously due to account restrictions, financial crime screening holds, or compliance checks.

Changes

    • breaking

      the request property's maxLength was decreased to 34

    • breaking

      the / response's property type changed from object to array for status

    • warning

      changed the pattern of the request property from ^[A-Za-z0-9.,\-\s]+$ to ^[a-zA-Z0-9\s,.-]{5,34}$

    • warning

      removed the optional property // from the response with the status

    • info

      added the required property to the response with the status