- Introduction
- Commands & Actions
- Transaction Sequence
- MasterPass
- Visa Checkout
- Foreign Exchange
- Parameter Description & Action
- Gateway Domain Knowledge
- Transaction Result Codes
-
Out Of Band
-
Out of band transaction notification
-
Out Of Band - Merchant Webservice
-
Card on File - Recurring/Adhoc transactions
-
PINBlock encryption via Triple DES DUKPT encryption
-
PINBlock encryption via Master/Session encryption
-
Track2 encryption via Master/Session encryption
-
Track2 encryption via Dukpt encryption
-
Debit with PIN and Balance Enquiry
-
EMV Transactions
-
Coding for EMV data
-
- Tokenization
- SOAP API
- Pos Device Intergration
- Acquire Contact Information
- 3D Secure
-
Enterprise API Samples
-
Transaction Message Examples
-
Merchant Benefits
-
Pre-Auth – “Authorisation with PAN”
-
3D Secure 2
-
Pre-Auth Completion – Follow-up Debit
-
3D Secure 2 implementation using the Pop-Up Method
-
Pre-Auth Reversal – “Authorisation Reversal”
-
3D Secure 2 implementation using the Form Post
-
Refund – “Follow-Credit”
-
Authorisation with 3DS 2 Data
-
Refund – “Initial Credit”
-
Void
-
- Card on File
- Additional Data Transactions
Authenticated collections are intended to enable a merchant who wants to make regular direct debits to a customer’s account to authenticate the customer.
This has two benefits:
- The merchant has proved that the customer has consented to these regular debits
- The customer has verified themselves by way of a pin validation so there is a higher level of comfort that the customer's account is a valid account and does belong to the customer.
Authenticated Collections is currently only available from Nedbank. In addition, the Authenticated Collections provider parameter must be enabled otherwise the transaction will be declined.
Coding for Authenticated Collection data
The following is a code snippet in C#:
enterprise.openElement("AuthenticatedCollectionData");
enterprise.setTag("AccountNumber", accountNumber);
enterprise.setTag("DebtorIdentification", debtorIdentification);
enterprise.setTag("MaximumCollectionAmount", maximumCollectionAmount);
enterprise.closeElement();
Note: That MerchantReference must be set for Authenticated Collections AND the transaction must be PIN authenticated card present. The MerchantReference is used as the contract reference. An AuthorisationCode is returned if successful.