How ACP Shared Payment Tokens Work Across Countries and What Stripe Charges
What an ACP Shared Payment Token Is and Where Stripe Accepts It
An ACP Shared Payment Token is a standardized way for payment processors like Stripe to store and reuse card information securely without keeping the full card number on file. Instead of your customer's card details living in your system, Stripe holds the token and you reference it for future charges. This matters because it reduces your security burden and lets customers authorize recurring or one-time payments without re-entering their card each time.
Stripe supports shared payment tokens in most countries where it operates, but not everywhere. The availability depends on local payment regulations, Stripe's banking partnerships in that region, and whether the card network (Visa, Mastercard, American Express) allows tokenization in that country. Stripe's coverage includes the United States, Canada, most of Europe, Australia, Japan, Singapore, and dozens of other nations—but some countries have restrictions or require different token formats.
Before you build a tokenization flow, check Stripe's current country list on their documentation site or contact their support team directly. Availability can shift as Stripe adds or removes regional support, and the rules differ between card-present (in-person) and card-not-present (online) transactions.
Key Takeaways
- Stripe supports shared payment tokens in most developed markets and many emerging ones, but you must verify your specific country before building token-based flows.
- Stripe charges the same processing fee for token-based payments as for regular card transactions—there is no separate token fee, but your standard interchange and assessment costs still apply.
- Token availability varies by card network, local regulation, and whether the transaction is online or in-person; some countries restrict how long tokens can be stored or require explicit customer consent.
- If Stripe does not support tokens in your country, you can still process payments but must collect card details fresh each time or use an alternative processor.
Stripe's Fees for Payments Using Shared Tokens
Stripe does not charge a separate fee for using a shared payment token. You pay the same processing rate whether the customer enters their card manually, you run a token-based charge, or they use a saved card from a previous transaction. In the United States, that is typically 2.9% plus $0.30 per transaction for online card payments, though rates vary by card type, industry, and your processing volume.
What you do pay are the underlying card network costs—interchange fees set by Visa and Mastercard, and assessment fees charged by the networks themselves. These costs are the same whether you use a token or a fresh card number. Stripe passes these through to you as part of your total processing fee. There is no hidden charge for storing or retrieving a token.
If you are processing in a country outside the United States, Stripe's base rate and the card network fees both change. European processors often see lower interchange rates due to regional caps, while some Asian and emerging markets have higher rates or different fee structures. Check your Stripe dashboard or pricing page for your specific country's rates.
Which Countries Allow Stripe Shared Payment Tokens
Stripe supports tokenization in the following regions with broad coverage: the United States, Canada, the United Kingdom, the European Union (including France, Germany, Spain, Italy, Netherlands, Belgium, Austria, Ireland, and others), Australia, New Zealand, Japan, Singapore, Hong Kong, and Mexico. Stripe also operates in Brazil, India, and several other emerging markets, though token support in those regions may be more limited or subject to additional compliance requirements.
Some countries have restrictions. For example, certain jurisdictions require that customers explicitly consent to token storage in writing, or that tokens expire after a set period (often one to three years). A few countries do not allow unscheduled recurring charges using tokens without fresh authorization each time. Russia, Iran, and a handful of other nations are not supported by Stripe at all due to sanctions or regulatory barriers.
The safest approach is to check Stripe's official country and region guide or contact their support team with your specific location. Availability can change, and the rules for what you can do with a token once stored vary significantly by region.
How Token Storage Rules Differ by Country
In the United States and Canada, Stripe can store tokens indefinitely as long as the account remains active and the card has not been reported as lost or stolen. The customer can revoke permission at any time, but there is no automatic expiration date.
The European Union has stricter rules. Under PSD2 (Payment Services Directive 2) and related regulations, tokens must be refreshed or re-authorized periodically, especially for unscheduled recurring charges. Some EU countries require explicit written consent before storing a token, and customers have the right to revoke it immediately. Tokens used for subscription billing may need to be re-validated annually or when the card expires.
Australia and other Commonwealth nations generally allow token storage similar to the US model, though some require clear disclosure to the customer about how long the token will be kept. Japan and Singapore have their own frameworks but generally permit long-term token storage with proper customer notification.
What Happens When a Country Is Not Supported
If Stripe does not support shared payment tokens in your country, you have several options. First, you can still process one-time payments with Stripe using fresh card details each time—tokenization is a convenience feature, not a requirement. Second, you can use Stripe's Payment Intent or Setup Intent APIs to handle card information securely without storing tokens yourself, though the customer will need to re-enter their card for each transaction.
Third, you can switch to a local payment processor that operates in your country and supports tokenization. Many regions have regional leaders—for example, 2Checkout (Verifone) in Europe, Adyen in multiple regions, or local processors in Asia and Latin America. These alternatives often have different fee structures and may support local payment methods (bank transfers, digital wallets, buy-now-pay-later services) that Stripe does not.
Fourth, if you are a business operating in an unsupported country but serving customers in supported countries, you can use Stripe's Connect platform to route payments through a supported region, though this adds complexity and may trigger additional compliance requirements.
Compliance and Security Considerations for Tokens Across Regions
Storing payment tokens means you are responsible for protecting them, even though Stripe holds the actual card data. You must comply with PCI DSS (Payment Card Industry Data Security Standard) requirements in your country. In most regions, using Stripe's tokenization actually reduces your PCI burden because you never touch the full card number—Stripe does.
However, some countries impose additional rules. The EU requires you to document how long you will keep tokens and to honor customer requests to delete them immediately. Some jurisdictions require you to notify customers if a token is compromised. A few countries mandate that tokens be encrypted at rest and in transit, which Stripe does by default, but you should verify this in your contract.
If you are storing tokens for subscription billing, you may need to obtain explicit consent before charging the token for the first time, and in some regions you must send a notification before each charge. These rules vary by country and sometimes by state or province within a country.
Frequently Asked Questions
Does Stripe charge extra to store a payment token?
No. Stripe charges the same processing fee whether you use a token or a fresh card number. You pay Stripe's standard rate (typically 2.9% plus $0.30 in the US) plus card network fees, regardless of how the card information reaches Stripe.
Can I use a Stripe token in a country where Stripe does not operate?
No. If Stripe does not support your country, you cannot use Stripe's tokenization service there. You would need to switch to a local processor or use Stripe only for customers in supported regions. Some businesses use Stripe Connect to route payments through a supported country, but this adds legal and operational complexity.
What happens to my tokens if Stripe closes my account?
Stripe will disable all tokens associated with your account. Any attempt to charge a token after account closure will fail. If you need to migrate to another processor, you cannot transfer the tokens themselves—you would have to ask customers to re-enter their card information with the new processor.
Do I need customer permission to store a token in Europe?
Yes, in most EU countries you must obtain explicit consent before storing a token, and you must clearly explain how long you will keep it and what you will use it for. Consent must be documented and the customer must be able to revoke it at any time. Rules vary by country, so check your local data protection authority's guidance.
Can I charge a stored token without asking the customer again?
In the United States and Canada, yes—once you have stored a token with consent, you can charge it for recurring subscriptions or one-time payments without re-asking. In Europe and some other regions, you may need to re-authorize the token periodically or send a notification before each charge, depending on local law and whether the charge is scheduled or unscheduled.