Similar to a payment
intent, you can use the createPaymentMethod
SDK function or send a POST request to the v1/payment-methods
endpoint of the payment methods API to create a payment method.
In the request body, include the payment method type
and card details. Set the usage value to
ON_SESSION if the customer wants to save the payment method
for future use. Include the following header parameters:
-
Toast-Session-Secret: The unique and randomized identifier for the payment or setup intent. This is returned in the response to create a payment or setup intent. -
Toast-Idempotency-Key: An integration-generated universally unique identifier (UUID) that is used to recognize retries of the same request.
Example request body
{
"type": "CARD",
"card": {
"number": "4242424242424242",
"cvv": "123",
"expiry": {
"month": "12",
"year": "27"
}
},
"billingDetails": {
"postalCode": "02118"
},
"usage": "OFF_SESSION"
}|
The type of payment method created. The value is:
|
|
|
The card details used to tokenize the payment card. |
|
|
The primary account number (PAN) of the card, which the API validates using the ISO-standard Luhn algorithm. |
|
|
Used to determine if the customer will save the payment method
for future use. Set the value to |
Example response body
{
"id": "f718c101-70e4-45fe-8fc1-67ba0a12a8c5",
"type": "CARD",
"usage": "OFF_SESSION"
"card": {
"firstSix": "411111",
"lastFour": "1111",
"expiry": {
"month": "12",
"year": "27"
},
"brand": "VISA",
"type": "VISA",
"fingerprint": "e19f9942-942b-4716-a45c-6ee69225970d",
"funding": "Debit",
[contents omitted]
}
}To create a payment method for merchant-initiated transactions,
you can use the createPaymentMethod
SDK function or send a POST request to the v1/payment-methods
endpoint of the payment methods API. In the request body, include the
payment method type and card details. Set the
usage value to OFF_SESSION to use for future
transactions or ON_AND_OFF_SESSION if the customer wants to
save the payment method to use for both customer and merchant-initiated
transactions. Include the following header parameters:
-
Toast-Session-Secret: The unique and randomized identifier for the payment or setup intent. This is returned in the response to create a payment or setup intent. -
Toast-Idempotency-Key: An integration-generated universally unique identifier (UUID) that is used to recognize retries of the same request.
Example request body
{
"type": "CARD",
"card": {
"number": "4242424242424242",
"cvv": "123",
"expiry": {
"month": "12",
"year": "27"
}
},
"billingDetails": {
"postalCode": "02118"
},
"usage": "OFF_SESSION"
}|
The type of payment method created. The value is:
|
|||||
|
The card details used to tokenize the payment card. |
|||||
|
The primary account number (PAN) of the card, which the API validates using the ISO-standard Luhn algorithm. |
|||||
|
Used to determine if the customer will save the payment method for future use.
|
Example response body
{
"id": "f718c101-70e4-45fe-8fc1-67ba0a12a8c5",
"type": "CARD",
"usage": "OFF_SESSION"
"card": {
"firstSix": "411111",
"lastFour": "1111",
"expiry": {
"month": "12",
"year": "27"
},
"brand": "VISA",
"type": "VISA",
"fingerprint": "e19f9942-942b-4716-a45c-6ee69225970d",
"funding": "Debit",
[contents omitted]
}
}