This operation can be used to evaluate spend control rules for a test transaction.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The audit user to log the request
Amount including currency
The transaction type.
RETAIL, ATM, UNIQUE, CASH_DISBURSEMENT, BALANCE_INQUIRY, P2P_DEBIT, P2P_CREDIT, CREDIT, CASHBACK A valid ISO-3166-1 alpha-3 country code.
"FIN"
Describes what method was used to verify the cardholder. The verification methods are limited to verification methods that are considered as valid verification methods according to strong customer authentication principles. Possible values: * WALLET - cardholder has been verified with the digital wallet device. * PIN - cardholder has entered the correct PIN of the card to the payment terminal. * BIO - cardholder has successfully been verified through a biometric method (e.g. fingerprint reader on card). * THREE_DS - cardholder has successfully been verified through 3DS.
WALLET, PIN, BIO, THREE_DS Describes how the card credentials were captured. Possible values:
UNKNOWN - the message from the merchant did not include a distinct method.MANUAL_ENTRY - the card credentials were manually entered by the merchant.MAGNETIC_STRIPE_READ - the magnetic stripe of the card was read by a terminal.CHIP_READ - the EMV chip of the card was read by a terminalCONTACTLESS - contactless transactions, i.e. the card credentials were read with near field communication (NFC) either from chip or digital wallet.ELECTRONIC_COMMERCE - the cardholder entered the card credentials as an e-com merchant.UNKNOWN, MANUAL_ENTRY, MAGNETIC_STRIPE_READ, CHIP_READ, CONTACTLESS, ELECTRONIC_COMMERCE VISA, MC REQUEST, ADJUSTMENT, SCHEME_ADVICE, REVERSAL_ADVICE