BVbvnk
Fiat Payments

Simulate pay-in

Changed on

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

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/v1/payins/simulate

Request

Request body

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

Payment method to be utilised for transactions. 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

amountAmount required(unresolved $ref)

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

  • 97d6c0d2fe2eRevision 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

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

    • info

      added the required property to the response with the status