Create and store a payment token with the appropriate credit/debit card information
Payment tokens are used to replace actual card data sent for processing a transaction. For example, you can store a card token with a customer and/or a subscription contract in your application and use the token to process a payment when required.
Parameters
The following fields are available to create a card token for all keyed/manually input credit/debit cards.
| parameter | description | required |
|---|---|---|
profile_id | merchant supplied customer id | No |
cnickname | a nickname that the cardholder would like to save | No |
creditcard | the credit card number | Yes |
cardfullname | the cardholder name printed or embossed on the front of the card | Yes |
month | the card expiration month | Yes |
year | the card expiration year | Yes |
baddress | the card billing street address (AVS) | No |
bcity | the card billing city name | No |
bstate | the card billing state code | No |
bzip | the card billing zip code (AVS) | Yes |
cphone | the cardholders phone number (mobile) | No |
cemail | the cardholders email address | No |
cvv | the card CVV - used for validation purposes only (CVV) | No |
store | set this to | No |
Note:Although it is optional to send the baddress parameter, it is recommended to send this parameter along with bzip to adhere to a full AVS check against a card purchase! This eliminates a downgrade fee for only having a partial AVS validation.
JSON Example
The following JSON example provides test values to create a card token with a manually input credit card. You can copy and paste these values in the Body Params section above to be used by the Try It feature
{
"transaction_data": {
"creditcard": "5544044490909090",
"month": "04",
"year": "19",
"cardfullname": "Jerry Smith",
"bzip": "46280",
"baddress": "26776 Chesterton Drive",
"bcity": "Indianapolis",
"bstate": "IN"
}
}References
- Payment Response Codes
Link to details on related response codes.