Incoming Transfer
Admin Access RequiredCreate an incoming transfer. The transfer_incoming_type must be specified (SWIFT_INCOMING for MT103 or SWIFT_FI_TO_FI_INCOMING for PACS.008) and the respective transfer type's payload be filled out in the request body. For SWIFT_INCOMING, the swift parameters must be completed. For SWIFT_FI_TO_FI_INCOMING, the swift_fi_to_fi parameters must be completed.
This endpoint is only available in our sandbox environment. It is not available in production.
This endpoint facilitates the simulation and testing of incoming transaction processing within the staging environment, enabling developers to validate transfer workflows without affecting production systems.
Two transfer types are supported:
SWIFT_INCOMING— MT103 incoming transfer. Uses theswiftpayload field.SWIFT_FI_TO_FI_INCOMING— PACS.008 FI-to-FI incoming transfer. Uses theswift_fi_to_fipayload field.
Example MT103 Incoming Transfer (SWIFT_INCOMING)
Example FI-to-FI Incoming Transfer (SWIFT_FI_TO_FI_INCOMING)
Authorization
AuthorizationRequiredBearer <token>Enter your token in the format: Bearer {token}
In: header
Request Body
application/jsonOptionaltransfer_incoming_typeRequiredstringenum, SWIFT_INCOMING (MT103 - will be deprecated) or SWIFT_FI_TO_FI_INCOMING (PACS.008 FI-to-FI)
"SWIFT_INCOMING" | "SWIFT_FI_TO_FI_INCOMING"swiftobjectMT103 incoming transfer payload. Required when transfer_incoming_type is SWIFT_INCOMING.
swift_fi_to_fiobjectPACS.008 FI-to-FI incoming transfer payload. Required when transfer_incoming_type is SWIFT_FI_TO_FI_INCOMING.
Response Body
Success response
transaction_idRequiredstring