Use external multi-pay tokens with Clover Ecommerce APIs
Clover supports external TransArmor® multi-pay tokens. Tokenization in ecommerce requires encrypting a customer's card as a token. Encryption conceals the content of card data to protect it from unauthorized access, while tokenization replaces sensitive data with a non-sensitive equivalent or token. Clover uses this card token as the source
to process secure payments with the Ecommerce APIs.
TransArmor (TA) tokens enhance transaction security by replacing sensitive cardholder data with randomly generated tokens, making decryption extremely difficult. They help reduce the scope of PCI-DSS compliance by removing sensitive data from the merchant’s environment and are easy to implement without requiring new hardware.
Get started
Create a new multi-pay token
Create a multi-pay token, such as a card-on-file (COF) token or a TransArmor® (TA) token.
Use an existing multi-pay token
Use your existing TransArmor token with the create a charge and pay for an order endpoints.
Terminology
Token type | Description |
---|---|
External token | An external token in Clover is generated by an external system, such as TransArmor®. This token can then be used within the Clover ecosystem for seamless integration and secure payment processing across different platforms. |
Single-pay token | A single-pay token in Clover, also known as a c-token, is a unique identifier for a one-time payment transaction. The token is alphanumeric and begins with clv_. Example: clv_1ABCDefgHI23jKL4m5nOPqR. When a payment is processed, this token is generated to securely represent the payment information without exposing sensitive card details. |
Multi-pay token | A multi-pay token in Clover allows multiple transactions using the same payment information. This type of token is particularly useful for recurring payments, subscriptions, or any scenario where you need to charge a customer multiple times without the need to re-enter their payment details each time. |
Related topics
Updated 13 days ago