Tokens are used to securely process payments without exposing sensitive card data.

However, token usage has specific limitations depending on how the token was created and the payment flow used.

External network tokens

When making a Charge API request with Guide
Seamless processing of network tokens for secure transactions. DPAN data, Solidgate does not generate a token, because:

• payments with DPAN are one-time payment
• Solidgate does not manage the lifecycle of this token

Always use the original DPAN for any subsequent payments by sending a new Charge API API request.

Digital wallets

When processing decrypted digital wallet payments Guide
Decrypt and handle Apple Pay tokens for payments Apple Pay or Guide
Decrypt and handle Google Pay tokens for payments Google Pay with is_decrypted: true , token returns are not provided. Since the data is decrypted on your side, Solidgate is not the token requester and does not receive the details necessary to generate a token for subsequent use.

The token is used for Guide
Merchant-Initiated Transactions (MIT) are payments initiated by the merchant without the customer being present, typically for recurring or scheduled payments. MIT transactions for recurring payments. As a result, card expiration updates are not received, and Guide
Explore Solidgate subscriptions for seamless recurring customer payments. subscriptions created in this way may be lost after the card expires.

In this case, it is recommended to use a flow with data encryption on Solidgate’s side is_decrypted: false , as card expiration updates are then received and subscriptions can seamlessly continue.