USAePay
API
Resolved
Storing a card for later — CustToken vs CardRef in USAePay?
Asked by Priya S. · 5/14/2026, 3:25:13 PM
Docs mention both CustToken and card ref number. Which do I use for stored-card charges?
Asked by Priya S. · 5/14/2026, 3:25:13 PM
Docs mention both CustToken and card ref number. Which do I use for stored-card charges?
Two different tokenization models — pick one and stick with it:
Customer object, attach one or more payment methods, and reference CustToken on future charges. Good when the same shopper has multiple cards, ACH accounts, and you want scheduled billing.API-wise:
// CustToken charge
{ "command":"cc:sale", "amount":"25.00", "custtoken":"cust_abc123" }
// CardRef charge
{ "command":"cc:sale", "amount":"25.00", "creditcard":{"cardref":"tok_xyz789"} }
Don't mix models per shopper — you'll end up with orphaned tokens. If you already have CardRefs and later need recurring, migrate them into a Customer with customer:addpaymentmethod.
We use CardRef for guest checkout and upgrade to CustToken the moment a shopper creates an account. Clean split.
Sign in to share what's worked for you.
Sign in