Interoperability with Ecommerce API

United States

If the merchant is configured for multipay tokens, you can use the card tokens created using the /v1/card/tokens endpoint for recurring card-not-present payments. This lets you build an integrated application where a customer's card data is captured in-person, and then charged in the future without being present.

To check if a merchant is set up for multipay tokens, send a GET request to the /v3/merchants/{mId}/gateway endpoint. In the response, check that the supportsMultiPayToken value is true. You can also see the merchant's credit card surcharge rate in the rate field.

curl --request GET \
  --url '{merchantUUID}/gateway' \
  --header 'accept: application/json'
  "accountName": "Sandbox Test Merchant",
  "supportsMultiPayToken": true,

See Creating and using a card token to learn how to create an ECOMM_COMPAT card token and use it to make a charge with the Ecommerce API.

Example use case

A retail store selling soaps offers a monthly soap subscription mailed to the customer's home. The initial charge is $20, and each month is an additional $15. A new customer enrolls in December for an annual subscription and pays the $20 charge in the store. This transaction uses the REST Pay API to take the payment and create a card token using a Clover device. Then, on the 1st of the each of the following 11 months, the merchant automatically charges the customer $15 for that month's soap delivery using the Ecommerce API /v1/charges endpoint. When the recurring charge is processed, the customer is automatically notified with an email receipt.