Cross-Border Push to Card | General Data Requirements

Follow most recent network updates at Bulletins.

Sender Data Requirements

To learn how to populate Sender Data in API, refer to Sender Name Push Transactions.

Sender's valid legal name, address, city, and country must be present on cross-border push to cards and U.S., and Canada domestic push to card transactions.

Note: for Cross-Border Clients, please email [email protected], or contact your TabaPay Representative for questions. The teams are working on updating our APIs for you and we will be in touch soon.

Data Element	Field	Data Requirement
Sender Legal Name (must be valid)	corresponding.name.first corresponding.name.first	Required
Sender Address including City and Country	corresponding.address	Required
Sender Date of Birth	corresponding.dateOfBirth	Required (from Oct 18 2024) - Date of birth with the format: YYYYMMDD. Sender must be at least 18 years old.
Sender Nationality	corresponding.nationality	Recommended (from Oct 18 2024) -- Sender Nationality using country codes.
Sender Occupation	corresponding.occupation	Recommended (from Oct 18 2024)- occupation of sender.
Sender Email Address	corresponding.email	Recommended (from Oct 18 2024) - Sender email (max of 40 characters)

Recipient Data Requirements

To learn how to populate Recipient Data in API, refer to Recipient Data Requirements.

Data Element	Data Requirement
Recipient Card Account Holder Address	Conditional; Must be accurate when present Street address is optional if you are doing their your sanction screening of recipients. State/Territory is required for US or Canadian recipients. Note: Recipient sanction screening is a network requirement and if you have recipients in US.
Recipient Card Account Holder Expiration Date	Optional; must be accurate and not expired when present
Recipient Card Account Holder CVV2	Optional; must be accurate when present
Recipient Email Address	Recommended (from Oct 18 2024)

Other Data Requirements

Data Element	Data Requirement	How to populate
Original Transaction ID of an AFT	Conditional; Required when the OCT is preceded by an AFT. Clients must provide this value regardless of whether the preceding AFT was processed via TabaPay or not.	See `corresponding.networkID`, refer to Network Transaction ID.
Source of funds	Required. Sender Source of Funds. Valid Values Include: Debit Card PrePaid Card Credit Card Cash Deposit Account Credit Account Mobile Money Account	Refer to Sender Data - Push Transactions.
Purpose of Payment	Depends on the corridor	Refer here
Merchant Address	Per the October 2024 Visa Mandate, Merchant Address is a required field on all OCTs - Domestic and Cross-border. TabaPay requires clients to pass this information via TabaPay's Unified Create Transaction API. Check this page on how you could pass this information.	Refer here

Country-Specific Data Requirements

Country	Data Requirements
Argentina	Purpose of Payment
Bangladesh	Purpose of Payment
Chile	Purpose of Payment
Colombia	Purpose of Payment
Originations from or going to Canada	Canadian Cross-Border Push Transactions
Egypt	Purpose of Payment
India	Purpose of Payment
Mexico	Purpose of Payment

Code Samples for Cross-Border OCTs

Here is an example for see the fields in a request.

22. Cross-Border OCT

Open Recipe