Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Transaction Management

Create Transaction

post

Provide all required data to the Merchant/PSP to build a transaction authorization request.

In case of network token, the token PAN, expiry date and cryptogram are provided.

In case of PCI token, the card PAN and expiry date are provided.

Header parameters
authorizationstring · min: 1 · max: 512Required

Technical identifier pre-defined at on-boarding that identifies the API consumer. Format shall be the string 'APIKEY' followed by a space and the api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b

x-correlation-idstring · min: 1 · max: 36Required

Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.

Body
tokenIdstring · min: 1 · max: 128Required

The token identifier.

Pattern: ^[a-zA-Z0-9_-]+$
transactionTypestring · enum · max: 64RequiredExample: SINGLEPossible values:
visaSignedPayloadstring · min: 1 · max: 4096Optional

Required only for Visa CTF and Visa CTF with DAF. Set with the signature (JWT) generated by Thales ETP SDK.

Responses
201

Created

application/json
transactionIdstring · min: 1 · max: 128Required

The unique transaction identifier.

encryptedDatastring · max: 8196Required

The payment credentials data encrypted in a JWE structure (see security section in the documentation).

Once decrypted, the JWE plaintext contains the following JSON object:

JSON field parameter namedescriptionMOCLength
dpanThe token PAN value provided for network token.CUp to 19
expThe token expiry date in the format MMYY provided for network token.C4
cryptogramThe payment cryptogram to use with the token for a payment. Presence of the cryptogram depends on the transaction type and the scheme.CUp to 256
fpanThe funding card PAN value. Only provided for PCI token.CUp to 19
fpanExpThe funding card expiry date in the format MMYY. Only provided for PCI token.C4

Example: {"dpan:"9580981500100002", "exp":"1222", "cryptogram": "45f8grzty7f4f5gs5s2c"}

ecistring · min: 2 · max: 2Optional

The Electronic Commerce Indicator. Payment System-specific value to indicate the results of the attempt to authenticate the cardholder. Provided only for Visa & Mastercard SCOF.

Example: 07
cryptogramExpiryDatestring · max: 64Optional

Cryptogram expiry date in ISO 8601. Provided for Visa only.

Example: 2021-09-27T17:06:09.000Z
isDAFbooleanOptional

If present and set to 'true', VISA confirms it is a Digital Authentication Framework transaction. Can be present only if the transaction type is 'VISA_DAF'.

Example: true
post/transactions

Create Transaction v2

post

Provide all required data to the Merchant/PSP to build a transaction authorisation request.

Header parameters
authorizationstring · min: 1 · max: 512Required

Technical identifier pre-defined at on-boarding that identifies the API consumer. Format shall be the string 'APIKEY' followed by a space and the api key value.
Example: APIKEY c03f88fe-01ba-11e8-ba89-0ed5f89f718b

x-correlation-idstring · min: 1 · max: 36Required

Technical identifier used for troubleshooting.
It helps on customer support when needed.
Each API request must be identified with a unique correlation Id.
It correlates the response and the request and eventually a notification if any.

Body
tokenIdstring · min: 1 · max: 128Required

The token identifier.

Pattern: ^[a-zA-Z0-9_-]+$
transactionTypestring · enum · max: 64Required

The request content depends on the transaction type.

Example: EMV_TOKENPossible values:
Responses
201

Created

application/json
transactionIdstring · min: 1 · max: 128Required

The unique transaction identifier.

encryptedDatastring · max: 8196Required

The payment credentials data encrypted in a JWE structure (see security section in the documentation).

Once decrypted, the JWE plaintext contains the following JSON object:

JSON field parameter namedescriptionMOCLength
dpanThe token PAN value provided for network token.CUp to 19
expThe token expiry date in the format MMYY provided for network token.C4
cryptogramThe payment cryptogram to use with the token for a payment. Presence of the cryptogram depends on the transaction type and the scheme.CUp to 256
fpanThe funding card PAN value. Only provided for PCI token.CUp to 19
fpanExpThe funding card expiry date in the format MMYY. Only provided for PCI token.C4

Example: {"dpan:"9580981500100002", "exp":"1222", "cryptogram": "45f8grzty7f4f5gs5s2c"}

ecistring · min: 2 · max: 2Optional

The Electronic Commerce Indicator. Payment System-specific value to indicate the results of the attempt to authenticate the cardholder. Provided only for Visa & Mastercard SCOF.

Example: 07
cryptogramExpiryDatestring · max: 64Optional

Cryptogram expiry date in ISO 8601. Provided for Visa only.

Example: 2021-09-27T17:06:09.000Z
isDAFbooleanOptional

If present and set to 'true', VISA confirms it is a Digital Authentication Framework transaction. Can be present only if the transaction type is 'VISA_DAF'.

Example: true
post/v2/transactions

Last updated

Was this helpful?