Transfers Statuses
Every possible status of a transfer order
When your users initiate transfer orders, transfers are going through a set of several statuses. You can find the list below:
Transfer status for a transfer | Description |
---|---|
submitted | The transfer order was created on Bridge side and will be sent to the bank after the user confirms it |
pending | The transfer order was confirmed by the user and is pending on Bridge side |
processing | The transfer order is being processed by Bridge |
transferring | Bridge just sent the transfer order to the bank and is waiting for the bank to send its response |
otp_sms_required | The bank requires a strong customer authentication (SCA) to initiate the transfer. Your user needs to validate the one time password sent by his bank. |
app2app_validating | The bank requires a strong customer authentication (SCA) to initiate the transfer. Your user needs to validate the app to app notification sent by his bank. |
initiated | The transfer order has been successfully sent to the bank. The bank should now execute the transfer within 1 open day |
otp_sms_invalid (final) | The transfer order failed because of a wrong OTP code filled by the user |
app2app_expired (final) | The transfer order failed because the user didn't accept the app to app strong customer authentication on time |
executed (final) | The transfer order was successfully executed by the bank and the funds have been transferred |
failed (final) | The transfer order failed or the transfer execution failed. You can check the reason in the field status_reason |
expired (final) | The transfer order has been stuck to a status other than a final one or initiated for more than 10 minutes |
unknown (final) | In very rare cases, a transfer can finish with a unknown status. It means we are not able to know if the transfer has been initiated or not. In this case, your users should check on their bank interface if the bank has taken the transfer into account |
When a transfer order failed (status = failed)
, you can get more details and check the failure's reason in the field status_reason
. This field depends on the information the banks share with us so the behavior might depend on the sender account's bank. Here is the possible data you can find in this field:
Status Reason | Decription |
---|---|
invalid_sender_account | The sender account selected for the transfer is not valid |
closed_sender_account | The sender account selected for the transfer is closed and cannot be used |
blocked_sender_account | The sender account is blocked and cannot be used |
not_authorized_for_sender_account | The transfer is not allowed with the sender account selected |
insufficient_funds_sender_account | The sender account doesn't have sufficient funds to initiate the transfer |
too_many_transfers | The user reached the maximum number of transfers allowed by their bank |
invalid_execution_date | The execution date is not valid |
transfer_cancelled_by_customer | The user cancelled the transfer |
technical_error | A technical error occurred |
regulatory_reason | The transfer has been refused by the bank |
not_specified | An error occurred |
invalid_receiver | The bank has not accepted the receiver |
invalid_credentials | The banks credentials the user provided don't allow us to make transfers from their account. The user needs to edit their credentials to re-synchronize their account and try again |
Updated over 2 years ago