Payment API
Account Details
- Overview
- Create an account
- Update an account
- Get account information
Authorisation Control
- Overview
- Authorisation Control Webhook
Authorisation Forwarding
- Overview
- Forward authorisation webhook
Card details
- Overview
- Create card
- Update card
- Get application
- Update application
- Get card
- Get plastic
- Get EMV scripts
- Update plastic
Customer
- Overview
- Get customer information
- Create a customer
- Update a customer
- Customer hierarchy
Exchange Rates API
- Overview
- Get ECB exchange rate
- Get ECB supported currencies
- Get FX exchange rates
ID
- Overview
- Initiate 3rd party authentication flow
- Callback to complete authentication flow
Instalment
- Overview
- Instalment Controller
Invoice
- Overview
- Get invoice information
- Update invoice information
Notification
- Overview
- Receive a notification
PIN
- Overview
- PIN operations with pre-shared key
- PIN operations using PKI
PIN Control
- Overview
- PIN Control handling
Purchase Details
- Overview
- Trigger repricing
- Get purchase details
- Create purchase details
- Update purchase details
RBA Forwarding
- Overview
- RBA forwarding
Repricing
- Overview
- Create repricing agreements
- Get repricing agreements
- Update repricing agreements
- Create price lists
- Get price lists
- Update price lists
Transaction
- Overview
- Test transactions
- Test authorizations
- Get transaction data
- Create transactions
- Create fees
- Update a transaction
- Batch payment
Transfer API
- Overview
- Post account to account transfer
- Account to account batch transfer
- Post card to card transfer
Wallet
- Overview
- Push Provision
- Activation data
- Get tokens
Test API
- Overview
- test-auth-request-templates
- test-authorizations
Hierarchy API
- Overview
- Card Hierarchy Management
- Card Hierarchy Group Management
- Card Management in Card Hierarchy Groups
Spend Control API
- Overview
- Rule Sets Endpoints
- Rules Endpoints
- Spend Control Test Endpoint
Generate retail ecommerce auth request template
Query Parameters
The audit user to log the request
Body
Request to generate retail ecommerce auth request
Data of the card with which the transaction is done with.
Unique ID of the card.
39Response
Request for generating ISO-8583 message and sending it immediately to processing system of Enfuce.
Data of the card with which the transaction is done with.
Unique ID of the card.
39The country of the merchants acquirer as a ISO-3166-1 alpha-3 country code. This can be used to identify if transaction is in scope of PSD2 regulation.
This code identifies the financial institution acting as the acquirer for the merchant.
11Merchant category code as per card scheme classification. Merchants classification is done based on the type of business or service they sell.
4The city where the transaction or withdrawal occurs.
13The country where the transaction or withdrawal occurs as a ISO-3166-1 alpha-3 country code.
A code that uniquely identifies a particular card acceptor, i.e. a merchant or a bank.
15Merchant name.
25Indicates if merchant will accept partial approval of amount. E.g. at a fuel pump the initial authorisation might be a predefined flat amount to which the issuer can respond an available amount smaller than the actual authorisation request. Note that this functionality is only available when card account balance resides at issuer.
A code that uniquely identifies a particular terminal at the merchant.
8Describes how the card credentials were captured. Possible values:
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.
MANUAL_ENTRY, MAGNETIC_STRIPE_READ, CHIP_READ, CONTACTLESS, ELECTRONIC_COMMERCE The transaction type. The only fully supported type is RETAIL. Other transaction types may be used, but no guarantees are made about their behaviour. Some transaction types have specific limitations:
ATM- In order to create ATM transactions,merchantData.merchantCategoryCodemust be6011. This behaviour is downstream from the VISA and MC authorization systems. If a different code is used, transactions will be treated asCASH
RETAIL, CASH, ATM, CREDIT, UNIQUE, P2P_CREDIT, P2P_DEBIT, BALANCE_INQUIRY