Skip to main content

​
Understanding Payment Tokens

When processing payments, you’ll encounter different types of tokens. This FAQ explains what they are, how they differ, and when you need to care about them.

​
What are Network Tokens?

Network tokens are card-brand tokens issued by Visa, Mastercard, American Express, or other card networks. They replace the PAN (Primary Account Number—the full card number) with a secure token. Key characteristics:
  • Processor-independent: Can be used with different payment processors
  • More secure: Don’t expose the actual card number
  • Better longevity: Automatically update when cards are replaced or expire
  • Higher approval rates: Card networks prefer network tokens
Why they matter: Network tokens help improve security and payment success rates. Revolv3 uses them automatically when available.

​
What are Processor Tokens?

Processor tokens are tokens created by a specific payment processor (like WorldPay, Adyen, or Nuvei). They can only be used with that specific processor. Key characteristics:
  • Processor-specific: Only work with the processor that created them
  • Direct routing: Useful when you need processor-specific features
  • Performance: Can be faster for repeat transactions with the same processor
When to use them: If you’re routing directly to a specific processor or need processor-specific features, processor tokens can be useful.

​
Which Tokens Does Revolv3 Create and Store?

Revolv3 is smart about tokens—we capture and store multiple token types to maximize flexibility and success rates:
  • PAN (Primary Account Number): The actual card number (stored securely as a fallback where required)
  • Processor tokens: Tokens from specific processors (WorldPay, Adyen, etc.)
  • Network tokens: Tokens from card networks (Visa, Mastercard, etc.)
Why store multiple types?
  • Flexibility: Can route to different processors as needed
  • Resilience: If one processor is down, can use another
  • Optimization: Choose the best token for each transaction based on success rates and costs
  • Fallback: Always have a backup if one token type fails
Think of it like having multiple keys to the same door—if one doesn’t work, you can try another.

​
Do I Need Processor Tokens if Revolv3 Creates Its Own Token?

Short answer: Yes, it’s helpful to keep processor tokens alongside Revolv3’s tokens. Why: Different tokens work better in different situations:
  • Revolv3 tokens: Work across multiple processors, great for flexibility
  • Processor tokens: Optimized for specific processors, can improve performance
  • Network tokens: Preferred by card networks, improve approval rates
Revolv3 automatically manages all of these for you. You don’t need to do anything special—we store the right tokens and use them automatically to optimize your payment success rates.

​
What is the “Revolv3 Token” / Payment Method ID?

The Revolv3 token (also called a paymentMethodId) is Revolv3’s internal representation of a payment method. It’s what you’ll use in your API calls to reference a stored payment method. What it contains:
  • May include the PAN (encrypted and secured)
  • Processor tokens (from various processors)
  • Network tokens (from card networks)
  • Additional security data (cryptograms, PAR data, etc.)
How you use it: Instead of sending full card details every time, you send the paymentMethodId: 
{
  "paymentMethodId": 6061,
  "Invoice": {
    "Amount": { "value": 10.00 }
  }
}
Why it’s useful:
  • Security: You never handle full card numbers after the first transaction
  • Convenience: Simpler API calls
  • Compliance: Reduces your PCI compliance scope
  • Performance: Revolv3 optimizes routing based on stored token data

​
Implementation Notes

​
What Should You Store?

Store only what you need:
  • ✅ Store the paymentMethodId that Revolv3 returns
  • ✅ Store your own customer reference IDs
  • ❌ Don’t store full card numbers or CVV codes
  • ❌ Don’t store processor tokens unless you have a specific need
Compliance: Keep token storage aligned with your compliance obligations (PCI DSS, GDPR, etc.).

​
Use API Responses as Source of Truth

The token fields returned by Revolv3’s API are what you should use. Don’t try to create or modify tokens yourself—let Revolv3 handle that.

​
For Recurring Billing

For subscriptions and recurring payments:
  • ✅ Store the paymentMethodId from the first successful payment
  • ✅ Use it for all future charges
  • ✅ Revolv3 automatically updates tokens when cards expire or are replaced (via Account Updater)
This gives you the best success rates for recurring billing.

​
Common Questions

Q: Do I need to understand all these token types? A: Not really. Revolv3 handles tokenization automatically. Just store the paymentMethodId we give you and use it for future transactions. Q: What if a token expires? A: Revolv3’s Account Updater service automatically updates expired tokens. You don’t need to do anything. Q: Can I use processor tokens directly? A: You can, but it’s usually better to use Revolv3’s paymentMethodId so we can optimize routing and handle fallbacks. Q: Are network tokens more secure? A: Yes, they’re more secure than storing PANs and they automatically update when cards are replaced.

​
Next Steps