Retrieves the correspondent bank transfer identified by the id path parameter.
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/correspondent_bank_transfers/{id}
- Mock serverhttps://api.weavr.io/_mock/products/multi/openapi/correspondent_bank_transfers/{id}
curl -i -X GET \
'https://sandbox.weavr.io/multi/correspondent_bank_transfers/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'api-key: YOUR_API_KEY_HERE'Success
The profile Id which a specific identity, instrument or transaction type is linked to.
Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.
You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.
Profile Ids can be found in the Multi Portal, in the API Credentials page.
The tag field is a custom field that can be used to search and filter.
An individual (natural person) originator of the transfer.
Travel Rule Requirements:
- Mandatory: Full name and account number (via bankAccountDetails)
- Mandatory: At least one supplementary information type (address + birth details, or address + official ID)
CBT-specific beneficiary details for SEPA/IBAN wire transfers with Banking Circle FI-to-FI field limits.
These details are passed to the beneficiary as the reference. This field is mandatory for wire transfers executed over SEPA. The allowed length is dependent on the payment type:
SEPA <= 35 characters. An extended character set is accepted to cater for all European languages. If SEPA does not support a particular character, it is automatically converted to an acceptable alternative, in line with SEPA scheme guidance.
Faster Payments <= 18 characters
Additional external data as key-value pairs.
The state of the correspondent bank transfer transaction, as follows:
- INVALID: The transfer has failed initial validation checks.
- PENDING_CHALLENGE: The transfer requires the completion of a transaction confirmation challenge before it can be submitted.
- SUBMITTED: The transfer has been submitted to the sending financial institution for processing.
- REJECTED: The transfer that was submitted was rejected.
- APPROVED: The transfer that was submitted has been approved and is being processed by the sending financial institution.
- FAILED: There was an issue with the transfer, and the transaction has failed.
- COMPLETED: The requested funds have been sent from the source instrument.
- RETURNED: The transfer has been returned to the sender.
- SCHEDULED: The transfer will be executed at the scheduled time.
- CANCELLED: The scheduled transfer has been cancelled.
- PENDING_CONFIRMATION: The transfer requires a manual confirmation by the user before proceeding.
The time when the transaction was created, expressed in Epoch timestamp using millisecond precision.
The epoch timestamp at which the transaction is scheduled to be executed.
The reason the scheduled transaction was cancelled.
{ "id": "string", "profileId": "string", "tag": "string", "sourceInstrument": { "type": "managed_accounts", "id": "string" }, "amount": { "currency": "str", "amount": 0 }, "originator": { "tag": "string", "name": "string", "address": "string", "country": "st", "bankAccountDetails": { … }, "supplementaryInformation": { … } }, "beneficiary": { "name": "string", "iban": "stringstringstr", "bankIdentifierCode": "stringst", "address": "string", "bankName": "string", "bankAddress": "string", "bankCountry": "st", "nationality": "st", "dateOfBirth": "2019-08-24" }, "purpose": "string", "description": "string", "externalData": [ { … } ], "state": "INVALID", "creationTimestamp": 0, "scheduledTimestamp": "string", "cancellationReason": "string", "validationOutcomes": [ { … } ] }