Verifone · Schema
VerificationAdvice
VerificationAdvice from Verifone eCommerce API
PaymentsPOSTerminal ManagementeCommerceFinTechPayment ProcessingOmnichannel
Properties
| Name | Type | Description |
|---|---|---|
| advice | string | |
| encrypted_card | string | The cardholder data encrypted using the Verifone provided public key. This can be obtained using either Verifone.JS solution or Verifone Checkout in capture mode. The data to encrypt is a JSON with po |
| public_key_alias | string | The alias for the public key used to encrypt this card. |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://raw.githubusercontent.com/api-evangelist/verifone/refs/heads/main/json-schema/ecommerce-api-verificationadvice.json",
"title": "VerificationAdvice",
"description": "VerificationAdvice from Verifone eCommerce API",
"type": "object",
"properties": {
"advice": {
"type": "string",
"enum": [
"3DS_REQUIRED"
]
},
"encrypted_card": {
"type": "string",
"title": "Client encrypted cardholder data",
"description": "The cardholder data encrypted using the Verifone provided public key. This can be obtained using either Verifone.JS solution or Verifone Checkout in capture mode.\n\n The data to encrypt is a JSON with possible tags being cardNumber, sequenceNumber, cardholderName, startMonth, startYear, expiryMonth, expiryYear, cvv. This should be a single JSON line and should not contain any spaces. Read <a target=\"_blank\" style=\"color:blue;\" href=\"https://docs.verifone.com/online-payments/api-integration-methods-auth-and-endpoints/secure-card-capture-key\">Secure card capture key</a> for details.\n\n Additionally, a tag called captureTime must be presenting indicating the time the card was captured in UTC in format RFC 3339, section 5.6. eg. 2019-08-24T14:15:22Z. Encrypted card is valid for only 15 minutes."
},
"public_key_alias": {
"type": "string",
"title": "Public Key Alias",
"description": "The alias for the public key used to encrypt this card."
}
}
}