Tokenization
Use Jupico tokenization to collect card, bank-account, and wallet payment details without exposing sensitive data to your platform.
Tokenization is the foundation of custom payment acceptance in Jupico. It replaces sensitive payment data with a token that your backend can use in Jupico APIs.
Use tokenization when your platform wants to own the payment page while keeping raw card and bank-account data out of your environment.
What tokenization does
When a customer enters payment information, Jupico securely receives the sensitive data and returns a tokenized representation. Your platform uses the token instead of the raw payment details.
Tokens can be used for:
- immediate card sales;
- authorizations and later captures;
- ACH/eCheck payments;
- saved payment methods;
- subscriptions;
- installments;
- wallet payments when configured.
Tokenization options
| Payment method | Component |
|---|---|
| Credit card | Credit Card Form |
| Bank account / ACH / eCheck | Bank Account Form |
| Apple Pay | Apple Pay web component |
| Google Pay | Google Pay web component |
All components are initialized from a browser authorization session created by your backend.
Token types
| Token type | Use for | Storage guidance |
|---|---|---|
| One-time token | Immediate payment execution. | Do not store for later use. |
| Reusable / permanent token | Future payments, subscriptions, installments, or stored payment methods. | Store only when the customer has authorized future use and your platform has appropriate controls. |
Basic flow
- Your backend creates a browser authorization session.
- Your front end renders one or more Jupico web components using that session.
- The customer enters payment details or selects a wallet.
- Jupico returns a tokenization result.
- Your front end sends the token to your backend.
- Your backend uses the token in the appropriate Jupico API call.
Best practice
Create one authorization session for the payment page and pass the same session object to all components on that page. Do not create separate sessions for card, bank account, Apple Pay, and Google Pay unless the payment context changes.