Sender Data

Learn how a payment sender relates to the API.

📘

Doing Payment Transactions/OCTs?

Sender Information is required on all Payment/OCT transactions for both Domestic and OCT transactions.

Card networks require Sender Information when performing a Money Transfer. This typically includes Name, City, and Country.

Please talk to your TabaPay Account Manager if you have questions.

Overview

There are certain use cases where a merchant may be required to send information about the person sending money to the recipient. For example, if Alice is sending money to Bob, Alice is considered a "Sender". The requirements around this information depend on the use case, corridor, and/or cross border vs domestic.

How do I send this information?

TabaPay's Unified Create Transaction API supports various types of transactions using the same end point. Sender name will be sent using either the corresponding object or the accounts.sourceAccount.owner object depending on whether the transaction is push or pull respectively.

Push transactions

In a push transaction, use the corresponding.name object in the Create Transaction API. Cross-border OCTs will require that the Corresponding Object be populated with Sender information including Name, Address, etc.

Pull transactions

In a pull transaction, use the accounts.sourceAccount.owner.name object in the Create Transaction API.

Push to Card

Domestic 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.

Cross-Border 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.

Instant Account Funding

Sender's valid legal name, address, city, and country is optional on account funding transactions.

📘

Instant Account Funding Transactions are always PULL transactions