Method: verifyCardWithZeroAmount

HTTP request
Request body
- JSON representation
Response body
VerifyCardWithZeroAmountResponse
- JSON representation
VerifyCardWithZeroAmountResultCode

Verifies a user's card without reserving any funds on it.

This method is called by Google to verify details of a user's card and to see if the card can be used for payments. No funds are reserved on the user's account.

If the endpoint encounters an error while processing the request, the response body from this endpoint should be of type ErrorResponse.

An example request looks like:


{
  "requestHeader": {
    "protocolVersion": {
      "major": 1,
      "minor": 0,
      "revision": 0
    },
    "requestId": "G1MQ0YERJ0Q7LPM",
    "requestTimestamp": "1481899949606"
  },
  "paymentIntegratorAccountId": "SpeedyPaymentsKorea_KRW",
  "card": {
    "accountNumber": "4123456789101112",
    "nameOnCard": "Example Customer",
    "expiryMonth": "01",
    "expiryYear": "20"
  },
  "merchantCategoryCodeNotPresent": {},
  "pin": "12",
  "dateOfBirth": "1990-01-01"
}

An example response looks like:


{
  "responseHeader": {
    "responseTimestamp": "1481899950236"
  },
  "cardNetworkResult": {
    "rawResult": {
      "scope": "VISA",
      "rawCode": "00"
    },
    "authorizationCode": "123456"
  },
  "addressVerificationResult": {
    "notSent": {
      "support": "UNSUPPORTED_BY_INTEGRATOR"
    }
  },
  "cvnResult": "NOT_SENT_UNSUPPORTED_BY_INTEGRATOR",
  "result": "SUCCESS"
}

HTTP request

POST https://www.integratorhost.example.com/integrator-base-path/v1/payment-integrator-korea-cards-api/verifyCardWithZeroAmount

Request body

The request body contains data with the following structure:

JSON representation

JSON representation
{ "requestHeader": { object (`RequestHeader`) }, "card": { object (`Card`) }, "addressVerificationData": { object (`AddressVerificationData`) }, "paymentIntegratorAccountId": string, "storedCredentialTransactionInformation": { object (`StoredCredentialTransactionInformation`) }, "pin": string, "connectingInformation": string, "dateOfBirth": string, "businessIdentifier": string, // The following is a list of mutually exclusive fields. At most one of the // fields will be set in a response: "merchantCategoryCode": string, "merchantCategoryCodeNotPresent": { object (`Empty`) } // End of mutually exclusive fields. }

{
  "requestHeader": {
    object (RequestHeader)
  },
  "card": {
    object (Card)
  },
  "addressVerificationData": {
    object (AddressVerificationData)
  },
  "paymentIntegratorAccountId": string,
  "storedCredentialTransactionInformation": {
    object (StoredCredentialTransactionInformation)
  },
  "pin": string,
  "connectingInformation": string,
  "dateOfBirth": string,
  "businessIdentifier": string,

  // The following is a list of mutually exclusive fields. At most one of the
  // fields will be set in a response:
  "merchantCategoryCode": string,
  "merchantCategoryCodeNotPresent": {
    object (Empty)
  }
  // End of mutually exclusive fields.
}

Fields
`requestHeader`	`object (RequestHeader)` REQUIRED: Common header for all requests.
`card`	`object (Card)` REQUIRED: Data about the user's payment card.
`addressVerificationData`	`object (AddressVerificationData)` OPTIONAL: The user's address to be verified by AVS.
`paymentIntegratorAccountId`	`string` REQUIRED: This is the payment integrator account identifier that identifies contractual constraints around this transaction.
`storedCredentialTransactionInformation`	`object (StoredCredentialTransactionInformation)` OPTIONAL: Information about usage of stored credentials.
`pin`	`string` OPTIONAL: The PIN used to verify the account holder. This is only passed for cases where it is necessary for verifying the card.
`connectingInformation`	`string` OPTIONAL: The connecting information (CI) that should be associated with this account. This is only passed for cases where it is necessary for verifying the card.
`dateOfBirth`	`string` OPTIONAL: Date of birth in 'YYYY-MM-DD' format for the account holder associated with the account. This is only passed for cases where it is necessary for processing the transaction.
`businessIdentifier`	`string` OPTIONAL: The business identifier that should be associated with the account. This is only passed for cases where it is necessary for verifying the card.
REQUIRED: The merchant category code, if available. The following is a list of mutually exclusive fields. At most one of the fields will be set in a response:
`merchantCategoryCode`	`string` This is the ISO 18245 merchant category code (MCC) identifying the type of goods/services being purchased by the user.
`merchantCategoryCodeNotPresent`	`object (Empty)` Indicates that the merchant category code is not present. This option is used specifically for certain regions (such as Korea) or cases where MCC is not required by the payment integrator.
End of mutually exclusive fields.

Response body

This method supports multiple return types. For additional information about what 4XX or 5XX HTTP status code to return with an ErrorResponse, consult the ErrorResponse object and HTTP status codes documentation.

Possible response messages
HTTP 200 Status	`object (VerifyCardWithZeroAmountResponse)`
HTTP 4XX / 5XX Status	`object (ErrorResponse)`
End of mutually exclusive fields.

VerifyCardWithZeroAmountResponse

Response object for the payment integrator hosted korea-cards-v1.verifyCardWithZeroAmount method.