INTERNATIONAL_TRANSFER
DefinitionCopied!
The INTERNATIONAL_TRANSFER
Transaction type is designed to handle and record the movement of funds across international borders.
Prerequisites for Transaction creationCopied!
For the creation of a transaction in the system, it is mandatory that the involved wallet and account are in an ACTIVE
status, and that there are enough funds to cover the transaction amount and any associated service fees. The related Beneficiary will need to be of type INTERNATIONAL
, be in status ACTIVE
and contain an active Payout Method.
Transaction Purpose
The transaction_purpose
field determines the valid reasons for initiating an international transfer through our API. The table below outlines the accepted purposes by country and transaction type.
Legend:
-
P2P - Person-to-Person
-
P2B - Person-to-Business
-
B2P - Business-to-Person
-
B2B - Business-to-Business
Purpose |
Canada |
Hong Kong |
India |
Philippines |
---|---|---|---|---|
|
P2P B2P |
P2P B2P |
P2P |
P2P |
|
P2P P2B B2P |
P2P P2B B2P |
P2P P2B B2P |
P2P P2B B2P |
|
P2P P2B B2P |
P2P P2B B2P |
P2P P2B B2P |
P2P P2B B2P |
|
P2P P2B B2P |
|||
|
P2P |
P2P B2P |
||
|
P2B B2B |
P2B B2B |
P2B B2B |
|
|
P2B B2B |
P2B B2B |
P2B B2B |
|
|
P2B B2B |
P2B B2B |
P2B B2B |
|
|
P2P B2P |
|||
|
P2B |
|||
|
P2B |
|||
|
P2P P2B B2P |
|||
|
P2P P2B B2P |
|||
|
P2B B2B |
P2B |
||
|
P2P P2B B2P B2B |
P2P P2B B2P |
P2P P2B B2P B2B |
|
|
P2B |
|||
|
P2B B2B |
P2B |
P2B B2B |
|
|
P2B |
|||
|
P2B |
|||
|
P2P P2B B2P |
|||
|
P2P P2B B2P B2B |
|||
|
B2B P2B |
|||
|
P2B B2B |
P2B B2P |
||
|
P2B B2B |
P2B |
||
|
P2B B2B |
P2B |
Source of funds
The
source_of_funds
field determines the valid The source of funds for the transaction. This field can only be sent in specific corridors . Allowed values are
EMPLOYMENT_INCOME
,OWNED_BUSINESS
,FAMILY_INCOME
,SAVINGS
,INVESTMENTS
,INHERITANCE
, PROCEEDS_OF_SALE
,PENSION
.
Transaction statusCopied!
The INTERNATIONAL_TRANSFER
transaction supports the following statuses:
Status |
Description |
---|---|
|
The transaction has been initialized in the system, serving as the inception point. |
|
At this stage, the transaction is in the midst of processing, typically when a ledger transaction necessitates a payment action. |
|
The transaction has been authorized and the funds are being transferred to the international financial institution. |
|
Funds have settled into the international financial institution. |
|
The transaction couldn't process, typically due to payment rejection, like a declined card transaction. |
|
A system glitch or anomaly that hindered the transaction's processing. |
|
The transaction was halted either by a customer or an agent via the Portal. |
|
An automated system rule resulted in the transaction's cancellation. |
|
This status signifies that the transaction is undergoing a thorough review by Alviere's compliance and risk department. |
|
The transaction is waiting for some action from the end customer. Currently only applicable in flows that require 3D-S authentication. |
|
After manual scrutiny, the transaction was declined by the risk and fraud department. |
Status reasonCopied!
INTERNATIONAL_TRANSFER
transactions can present a status reason if a failure occurs due to issues with the payment method utilized for funding the transaction, and will inherit the reason from the corresponding child passthrough transaction, namely CARD_PASSTHROUGH
and BANK_PASSTHROUGH
. Possible status_reason
values for these transactions are equivalent to the ones applicable to the LOAD_FUNDS
transaction type.Other possible status reasons are below:
Here is the updated markdown table with the items in the first column enclosed in backticks:
Status Code |
Description |
---|---|
|
The Payout method account number is incorrect or invalid. |
|
The Beneficiary's account has been closed. |
|
The Beneficiary's account is not eligible to receive payments. |
|
Incorrect or invalid Payout method account details provided for the transaction. |
|
The account name does not match the Beneficiary’s name. |
|
A system error occurred within the service provider's system. |
|
The transaction amount is incorrect or invalid. |
|
The bank name provided for the transaction is incorrect. |
|
The Beneficiary's identification is incorrect or invalid. |
|
The Beneficiary's name does not match the provided details. |
|
The Beneficiary has exceeded their transaction limit. |
|
The branch details provided are incorrect or invalid. |
|
The transaction failed due to compliance regulations or checks. |
|
The correspondent bank's limit has been exceeded for this transaction. |
|
The International Bank Account Number (IBAN) is incorrect or invalid. |
|
The bank code provided for the transaction is incorrect. |
|
The selected payout method is not currently active. |
|
The transaction has expired and can no longer be processed. |
|
The Beneficiary is a minor and ineligible to receive the transaction. |
|
Required documents for the transaction are missing. |
|
A refund has been requested for the transaction. |
|
The transaction is blocked due to sanctions against the beneficiary's country. |
|
The address provided for the account is incorrect or invalid. |
|
The end customer needs to go through the 3D-S authentication flow in order to authorize the transaction. |
|
The card is not 3D Secure (3D-S) enabled. |
|
Cardholder failed 3DS authentication. |
|
Initial 3DS transaction not completed within 15 minutes. |
|
3DS system malfunction. |
|
3DS authentication required. |
|
3DS authentication service provided invalid authentication result. |