Documentation changes for October 5, 2026
As part of an ongoing effort to better align the documentation with the API, we’ve corrected the TokenStorage response examples and schemas. These changes affect the documentation only; the API was already returning this data.
Corrected referenceId in TokenStorage response examples
The response examples showed referenceId as a transaction ID. When you save a payment method, referenceId and methodReferenceId both return the stored method ID, and resultText is Added. Use referenceId as the storedMethodId, because the response doesn’t include methodReferenceId when you convert a temporary token to a permanent token. When you update or remove a payment method, referenceId returns the methodId from the request path. This affects the following endpoints:
See Save a payment method with the API to learn more.
Corrected customer fields on stored method responses
The documentation described the customers object with payor request fields, but the API returns the customer record. We’ve documented firstname, lastname, email, phone, address, address1, city, state, zip, country, shippingAddress, additionalFields, customerEvents, and customerPortal. We’ve removed firstName, lastName, the billing* fields, shippingAddress2, and additionalData, which the API doesn’t return. This affects the following endpoints:
Documented additional fields on TokenStorage responses
The TokenStorage responses now document fields the API already returns. Save a payment method returns pageIdentifier on successful requests, and authCode, avsResponseText, cvvResponseText, and vendorId on declined requests. Get a payment method returns walletType. This affects the following endpoints: