Community
Clarifying destinationAccount, sourceAccount, destinationAccountID and sourceAccountID.
When creating transactions, it is important to be PCI-Compliant and follow best practices for passing payment details and personally identifiable information PII.
Each of the source or destination fields can be found in the glossary as well as the Create Transaction API under the Accounts Object. You can learn more about Account IDs on TabaPay Tokens.
How you include your card or bank information in the request determines what fields you may use. Including the full payment information may also be referred to as "card in the clear" or "bank data in the clear".
Using
destinationAccountID
means you cannot use thedestinationAccount
in the request. Equally,sourceAccountID
is incompatible withsourceAccount
Push Transaction
Field | Push Transaction with Full Card or Bank Info | Push Transaction with Account IDs |
---|---|---|
destinationAccount | Contains the full card, or bank account information. | - |
sourceAccount | N/A | N/A |
destinationAccountID | - | Contains the tokenized card, or bank information as a unique ID. |
sourceAccountID | Contains your settlementAccountID. | Contains your settlementAccountID. |
- N/A (Not Applicable) indicates that the sourceAccount field does not apply to push transactions (i.e. leave it out). TabaPay requires you to provide your settlementAccountID value for the sourceAccountID field.
Push Transaction with Full Card Info
For a full example, refer to the recipe 23. B2C Push Transaction .
{
"accounts": {
"sourceAccountID": "6iaCQHYOvAQKW59FNUDG4U",
"destinationAccount": {
"card": {
"accountNumber": "4111111111111111",
"expirationDate": "202708"
},
"owner": {
"name": {
"first": "Test",
"last": "Name"
}
}
}
},
"memo": "Payment to Bank Account B",
"referenceID": "1kdevt07232024",
"type": "push",
"amount": "2.00"
}
Push to Card with Accounts
For a full example, refer to the recipe, 9.1 Push to Card with Accounts .
{
"accounts": {
"sourceAccountID": "6iaCQHYOvAQKW59FNUDG4U",
"destinationAccountID": "22_Character_TabaID12"
},
"memo": "Payment to Bank Account B",
"referenceID": "15character1234",
"type": "push",
"amount": "2.00"
}
Pull Transaction
Field | Pull Transaction with Full Card or Bank Info | Pull Transaction with Account IDs |
---|---|---|
destinationAccount | N/A | N/A |
sourceAccount | Contains the raw card info or bank account information. | - |
destinationAccountID | Contains your settlementAccountID. | Contains your settlementAccountID. |
sourceAccountID | - | Contains the tokenized card, or bank information as a unique ID. |
- N/A (Not Applicable) indicates that the destinationAccount field does not apply to pull transactions (i.e. leave it out). TabaPay requires you to provide your settlementAccountID value for the destinationAccountID field.
Pull Transaction using Full Card or Bank Info
For a full example, refer to the recipe, 12. Create Pull Transaction with Card Info .
{
"accounts": {
"sourceAccount": {
"card": {
"accountNumber": "4111111111111111",
"expirationDate": "202708",
"securityCode": "232"
},
"owner": {
"name": {
"first": "Test",
"last": "Name"
},
"address": {
"line": "123 Street",
"city": "San Francisco",
"state": "CA",
"zipcode": "94103",
"country": "840"
}
}
},
"destinationAccountID": "7c2Ju7e2awxBTLLLN24kQN"
},
"type": "pull",
"amount": "1.00",
"referenceID": "kdevtest123"
}
Pull Transaction with Accounts
For a full example, refer to the recipe, 13. Pull Transaction with Accounts.
{
"accounts": {
"sourceAccountID": "BikavmpEWcDxHodMwv5g3A",
"destinationAccountID": "tyQ1i2nYA2NL4E3pBxWira"
},
"referenceID": "kdt0625a24",
"type": "pull",
"amount": "1.08",
}'