AccountDetails
Stay organized with collections
Save and categorize content based on your preferences.
Contains data related to the user's payment card.
| JSON representation |
{
// Union field account_representation can be only one of the following:
"card": {
object (Card)
},
"paymentToken": {
object (PaymentToken)
}
// End of list of possible types for union field account_representation.
} |
| Fields |
Union field account_representation. REQUIRED: The card details. account_representation can be only one of the following: |
card |
object (Card)
Representation of a card in its physical format (i.e. the FPAN).
|
paymentToken |
object (PaymentToken)
Representation of a card that has been tokenized by the network.
|
PaymentToken
The representation of a card after it has been tokenized by the network.
| JSON representation |
{
"nameOnCard": string,
"paymentTokenAccountNumber": string,
"expiryMonth": string,
"expiryYear": string,
"cryptogram": string
} |
| Fields |
nameOnCard |
string
REQUIRED: The customer's name as it appears on the card.
|
paymentTokenAccountNumber |
string
REQUIRED: The account number for the payment token.
|
expiryMonth |
string
OPTIONAL: Expiration month, formatted MM.
|
expiryYear |
string
OPTIONAL: Expiration year, formatted YY.
|
cryptogram |
string
OPTIONAL: The single-use key generated by the token provider for the transaction.
|
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-02-28 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-28 UTC."],[[["This document describes data structures related to user payment card information."],["It defines two ways to represent card details: `card` for physical cards and `paymentToken` for tokenized cards."],["`PaymentToken` stores tokenized card data, including name, account number, and optional expiry and cryptogram."],["Both representations are part of the `account_representation` field, which is required."]]],["The document details data structures for card payment representations. It defines a union field `account_representation`, which can be either a `card` (physical card details) or a `paymentToken` (tokenized card). `PaymentToken` includes fields like `nameOnCard`, `paymentTokenAccountNumber` (both required), and optional `expiryMonth`, `expiryYear`, and `cryptogram`. This data is essential for processing transactions using either physical cards or network-tokenized versions.\n"]]