v1

latestOpenAPI 3.0.12026-07-2421268219.4 KB
/v1/transactions

Validate an existing alias

An existing alias can be validated at any time with the transaction validate API. No amount will be blocked on the customers account. Only credit cards (including Apple Pay and Google Pay), PFC, KLN and PAP support validation of an existing alias.

post/v1/transactions/validate

Request body

refnostring required

The merchant's reference number. It should be unique for each transaction.

refno2string

Optional customer's reference number. Supported by some payment methods or acquirers.

currencystring required

3 letter <a href='https://en.wikipedia.org/wiki/ISO_4217' target='_blank'>ISO-4217</a> character code. For example CHF or USD

Example request

{
  "card": {
    "alias": "AAABeCBPbiHssdexyrAAAYkaznYWAPYt",
    "number": "4242424242424242"
  },
  "PFC": {
    "alias": "AAABeCBPbiHssdexyrAAAYkaznYWAPYt"
  },
  "KLN": {
    "alias": "AAABeCBPbiHssdexyrAAAYkaznYWAPYt"
  },
  "PAP": {
    "alias": "AAABeCBPbiHssdexyrAAAYkaznYWAPYt"
  },
  "ESY": {
    "alias": "AAABeCBPbiHssdexyrAAAYkaznYWAPYt"
  }
}

Response

Alias successfully validated

transactionIdstring

The transactionId to use for subsequent actions like settlement.

acquirerAuthorizationCodestring

The authorization code returned by the acquirer or payment method provider.

accertifyAccertify

Accertify decision (Accepted, Review, Declined

Example response

{
  "card": {
    "alias": "AAABeCBPbiHssdexyrAAAYkaznYWAPYt"
  }
}