The representation of a GUID, generally the id of an element. The bank card types. Credit card Debit card The bank account type. A credit card. A debit (cheque or savings) card. The supported payment services. A real-time card not present transaction. A real-time card not present transaction. A mail order / telephone order transaction. A recurring mail order / telephone order transaction. A batch card not present transaction. A payD mobile payment transaction. A MasterPass payment transaction. A WiCode payment transaction. A Sid payment transaction. A SnapScan payment transaction. A EftSecure payment transaction. A Zapper payment transaction. An MPGS real time payment transaction. An MPGS payment transaction. An MPGS payment transaction with no 3DS. An recurring MPGS payment transaction with no 3DS. A Masterpass Remote API transaction. An Electrum Remote API transaction. A card verification transaction. An eBucks payment transaction. A digital wallet Google Pay transaction. A digital wallet Google Pay recurring transaction. A digital wallet Apple Pay transaction. A digital wallet Apple Pay recurring transaction. A digital wallet Samnsung Pay transaction. A digital wallet Samsung Pay recurring transaction. The transaction status types. The transaction was success. The transaction failed. Please see the ResponseDetail element for more detail. The merchant verification action. A Full Authentication processes both 3D request to Bankserv and the authorize request to the acquirer A Non-Payment Authentication does not process the authorize request to the acquirer,it turns it around within the gateway and returns result to merchant. A Payment Authentication only processes an authorization to the acquirer The network token status. The network token status is not applicable i.e this token does not have a status The PAN was successfully tokenized The PAN failed tokenization A bank account definition. The acquiring bank. The accountholder name. The Branch Code. The Account Number. The Account Type. An address definition. The first address line. Typically a business or apartment complex name. The second address line. Typically a street name and number. The city name. The address neighbourhood. The post or zip code. The province or state. The country numeric code according to the ISO 3166-1 standard. A bank card definition. A token that can be used to identify the captured card in subsequent transactions. The card association. The type of bank card (debit or credit). The cardholder name printed on the card. The bank card number. The card expiry month. The card expiry year. The card security code (CSC / CVV / CVD). Field for token Cryptogram. A collection of additional information regarding the method response. The service that generated the transact result code. The transaction result code. The transaction result description. A user-friendly message that can be relayed to the end-user. A unique identifier to identify the stored card details The cardholder name printed on the card. The masked bank card number. The card expiry month. The card expiry year. An identifier for whether the token has been verified previously. This field indicates the Visa tokenization status of a card. e.g. If a card has been successfully tokenized by Visa, if the tokenization failed or if the tokenization is not applicable. The network token failure reason. The network token failure Message. The merchant's identifier for the user The cardholder name printed on the card. The masked bank card number. The card expiry month. The card expiry year. An identifier for whether the token has been verified previously. Secure 3D Data definition. The Cardholder Authentication Verification Value. It is a Visa Secure-specific cryptographic value that is created by an Issuer ACS during Visa Secure authentication. Electronic Commerce Indicator is a value returned by Directory Servers (namely Visa, MasterCard, JCB, and American Express) indicating the outcome of authentication attempted on transactions enforced by 3DS. Indicates the 3D Secure authentication result for the transaction. MdStatus tells whether the cardholder was successfully authenticated, an authentication attempt was made, or authentication failed/was not completed The flag to indicate the transaction enrolment status. The flag to indicate Payer Authentication Response. The transaction ID from the 3D Secure provider. The value to determine the 3D secure version to used or to be used for Authentication. The Directory Server Transaction ID from the 3D Secure provider. This is commonly a string in UUID format. The value determining the Authntication type of the transaction. A unique identifier to identify the merchant's payment profile. A unique identifier to identify the transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization amount in the lowest monetary unit. The currency code according to the ISO 4217 standard. The transaction order or reference number. The URL that the consumer will be redirected to once the transaction is complete. A description of the transaction being performed or goods being purchased. The cart items being purchased. The channel via which the purchase is being performed. Accepts values of app, web or mobi. Whether shipping is requested or not. The mobile network of the customer performing the Network purchase. The mobile phone number of the customer performing the Network purchase. The QR Code being used for the Network Code purchase. A unique identifier to identify the transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The MasterPass redirect URL The transaction status (Success or Fail) The transaction result code. A unique identifier to identify the merchant's payment profile. The merchant's identifier for the user The card details. A unique identifier to identify the stored card details The transaction status (Success or Fail) This field indicates the Visa tokenization status of a card. e.g. If a card has been successfully tokenized by Visa, if the tokenization failed or if the tokenization is not applicable. The network token failure reason. The network token failure Message. The transaction result code. A unique identifier to identify the merchant's payment profile. The merchant's identifier for the user A unique identifier to identify the merchant's payment profile. A unique identifier to identify the merchant's payment profile. The merchant's identifier for the user The card details. The transaction status (Success or Fail) The transaction result code. A unique identifier to identify the merchant's payment profile. A unique identifier to identify the transaction. A unique identifier to link split payments A unique identifier to identify a preceding transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization amount in the lowest monetary unit. The currency code according to the ISO 4217 standard. The payment payback period. Available for bank cards with a budget facility. The transaction order or reference number. The authorization code received from the payment service. The target payment service. The card details. The card bank account type. The customer first name. The customer last name. The billing address. The shipping address. The merchant address. The customer email. The customer mobile phone number. The customer home phone number. The customer work phone number. The PARes Payload obtained through the 3D Secure authentication process. The ACS response to the CReq message. It can indicate the result of the Cardholder authentication or, in case of an App-based model, also signal that further Cardholder interaction is required to complete the authentication The TerminalID to be passed in Postilion field 41 for Card transactions. If left blank, the configured value will be used. The CardAcceptorName to be passed in Postilion field 43 for Card transactions. If left blank, the configured value will be used. Flag to indicate that the card is going to be tokenized, used to indicate a initial recurring payment Flag to indicate that the transaction is as part of a trial subscription The MerchantCategoryCode to be passed in Postilion field 18 for Card transactions. If left blank, the configured value will be used. An identifier allowing a merchant to indicate which specific CIT i.e. customer initiated or MIT i.e. merchant initiated transaction is being performed The merchant verification action. The merchant phone number. If left blank, the configured merchant phone number value will be used. The merchant website URL. If left blank, the configured merchant website URL value will be used. The Submerchant ID uique to provide for merchant aggregation. The Secure 3D Data for merchant transaction. A unique identifier to identify the merchant digital wallet payment profile. Base64-encoded digital wallet payload (decoded bytes limited to 8192). The merchant customer service phone number is the hotline of the merchant, can be blank. A unique identifier to identify the transaction. A unique identifier to link split payments The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization code received from the payment service. The transaction status (Success or Fail) The transaction result code. The amount authorized by the bank. A unique identifier to identify the merchant's payment profile. A unique identifier to identify the transaction. A unique identifier to link split payments A unique identifier to identify a preceding transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The initial authorization amount or the amount to be added to the initial authorization if the InitialAuthRef is provided (in the lowest monetary unit). The currency code according to the ISO 4217 standard. The payment payback period. Available for bank cards with a budget facility. The transaction order or reference number. The authorization code received from the payment service. The Initial Authorization Reference received from the payment service. The target payment service. The card details. The card bank account type. The customer first name. The customer last name. The billing address. The shipping address. The merchant address. The customer email. The customer mobile phone number. The customer home phone number. The customer work phone number. The PARes Payload obtained through the 3D Secure authentication process. The ACS response to the CReq message. It can indicate the result of the Cardholder authentication or, in case of an App-based model, also signal that further Cardholder interaction is required to complete the authentication The TerminalID to be passed in Postilion field 41 for Card transactions. If left blank, the configured value will be used. The CardAcceptorName to be passed in Postilion field 43 for Card transactions. If left blank, the configured value will be used. Flag to indicate that the card is going to be tokenized, used to indicate a initial recurring payment Flag to indicate that the transaction is as part of a trial subscription The MerchantCategoryCode to be passed in Postilion field 18 for Card transactions. If left blank, the configured value will be used. An identifier allowing a merchant to indicate which specific CIT i.e. customer initiated or MIT i.e. merchant initiated transaction is being performed The merchant phone number. If left blank, the configured merchant phone number value will be used. The merchant website URL. If left blank, the configured merchant website URL value will be used. The Submerchant ID uique to provide for merchant aggregation. The Secure 3D Data for merchant transaction. A unique identifier to identify the transaction. A unique identifier to link split payments The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization code received from the payment service. The Initial Authorization Reference received from the payment service. The transaction status (Success or Fail) The transaction result code. The amount authorized by the bank. A unique identifier to identify the merchant's payment profile. A unique identifier to identify the transaction. A unique identifier to link split payments A unique identifier to identify a preceding transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization amount in the lowest monetary unit. The unique eBucks token relating to this payment. The currency code according to the ISO 4217 standard. The transaction order or reference number. The target payment service. A unique identifier to identify the transaction. A unique identifier to link split payments The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization code received from the payment service. The transaction status (Success or Fail) The transaction result code. The message timestamp. A unique identifier to identify the message. A identifier to identify the source of the message. A unique identifier to identify the merchant's payment profile. A unique identifier to identify the transaction. A unique identifier to link split payments A unique identifier to identify a preceding transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization amount in the lowest monetary unit. The currency code according to the ISO 4217 standard. The payment payback period. Available for bank cards with a budget facility. The transaction order or reference number. The authorization code received from the payment service. The target payment service. The card details. The card bank account type. The customer first name. The customer last name. The billing address. The shipping address. The merchant address. The customer email. The customer mobile phone number. The customer home phone number. The customer work phone number. The PARes Payload obtained from the 3D Secure authentication process. The ACS response to the CReq message. It can indicate the result of the Cardholder authentication or, in case of an App-based model, also signal that further Cardholder interaction is required to complete the authentication The TerminalID to be passed in Postilion field 41 for Card transactions. If left blank, the configured value will be used. The CardAcceptorName to be passed in Postilion field 43 for Card transactions. If left blank, the configured value will be used. Flag to indicate that the card is going to be tokenized, used to indicate a initial recurring payment Flag to indicate that the transaction is as part of a trial subscription The MerchantCategoryCode to be passed in Postilion field 18 for Card transactions. If left blank, the configured value will be used. An identifier allowing a merchant to indicate which specific CIT i.e. customer initiated or MIT i.e. merchant initiated transaction is being performed The merchant verification action.PaymentAuthentication,NonPaymentAuthentication or Payment The merchant phone number. If left blank, the configured merchant phone number value will be used. The merchant website URL. If left blank, the configured merchant website URL value will be used. The Submerchant ID uique to provide for merchant aggregation. The Secure 3D Data for merchant transaction. A unique identifier to identify the merchant digital wallet payment profile. Base64-encoded digital wallet payload (decoded bytes limited to 8192). The merchant customer service phone number is the hotline of the merchant, can be blank. A unique identifier to identify the transaction. A unique identifier to link split payments The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization code received from the payment service. The transaction status (Success or Fail) The transaction result code. The amount authorized by the bank. A unique identifier to identify the merchant's payment profile. A unique identifier to identify the transaction. A unique identifier to identify a preceding transaction. An identifier to link payments ie split payments and refunds. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization amount in the lowest monetary unit. The currency code according to the ISO 4217 standard. The transaction order or reference number. The target payment service. The unique eBucks token relating to this payment. The card details. The bank account details. The card bank account type. The customer first name. The customer last name. The billing address. The shipping address. The merchant address. The customer email. The customer mobile phone number. The customer home phone number. The customer work phone number. The TerminalID to be passed in Postilion field 41 for Card transactions. If left blank, the configured value will be used. The CardAcceptorName to be passed in Postilion field 43 for Card transactions. If left blank, the configured value will be used. The MerchantCategoryCode to be passed in Postilion field 18 for Card transactions. If left blank, the configured value will be used. An identifier allowing a merchant to indicate which specific CIT i.e. customer initiated or MIT i.e. merchant initiated transaction is being performed The Submerchant ID uique to provide for merchant aggregation. A unique identifier to identify the transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization code received from the payment service. The transaction status (Success or Fail) The transaction result code. A unique identifier to identify the merchant's payment profile. A unique identifier to identify the transaction. A unique identifier to identify a preceding lookup transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The authorization amount in the lowest monetary unit. The currency code according to the ISO 4217 standard. The transaction order or reference number. The Master Pass Remote API transaction id that was returned on the generateTransactionId request (Mandatory parameter for MPRAPI PaymentService) The card details. The merchant verification action. The target payment service. Term Url for MPGS authentication redirect 3DS Server internal transaction id The v4 or v6 customer IP address of the of the machine where the browser is running on. The screen height in pixels of the customers browser. The screen width in pixels of the customers browser. The Secure 3D Data for merchant transaction. A unique identifier to identify the merchant digital wallet payment profile. Base64-encoded digital wallet payload (decoded bytes limited to 8192). It indicates if the 3DS Method (a script that collects browser/device data for frictionless authentication) finished successfully. A unique identifier to identify the transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The transaction status (Success or Fail) The transaction result code. Indicates whether the cardholder is enrolled for 3D Secure. The fully qualified Issuer ACS URL. This is used by the merchant to redirect the cardholder. Returned if the cardholder is enrolled. The encoded PAReq generated by MAPS. Returned if the cardholder is enrolled. The Masterpass secure code identifier value that must be used on the purchaseTransactionId request to complete the purchase when the authentication type is 3D-Secure End status of the transaction mdStatus field provides all the information that is needed to determine how to manage the transaction in the merchant system. 3DS Server internal transaction id A complete html fragment that needs to be rendered in user browser when mdStatus=50 ACS redirect form raw HTML, containing all the required parameters to be posted to ACS or SecurePlus. PAReq, termURL, MD and ACS url itself. Form should be presented to user as is. A unique identifier to identify the merchant's payment profile. A unique identifier to identify the transaction. A unique identifier to identify a preceding transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The transaction order or reference number. The Master Pass Remote API transaction id that was returned on the generateTransactionId request (Mandatory parameter for MPRAPI PaymentService) The unique eBucks token relating to this payment. Partial voiding of the incremental Authorization by revising the amount, needs to be accompliced with the InitialAuthRef to link it to the pre authorization. The amount here must be the Revised (lower) value for the authorization . Example: if the initial estimated transaction amount is 1000 cent and the merchant wants to decrease the estimated amount by 200 cent before sending a completion/clearing transaction. Then, the value for this field should be 800. The Initial Authorization Reference received from the payment service. The target payment service. A unique identifier to identify the transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The transaction status (Success or Fail) The transaction result code. A unique identifier to identify the merchant's payment profile. A unique identifier to identify the transaction. A unique identifier to identify a preceding transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The transaction order or reference number. The Master Pass Remote API transaction id that was returned on the generateTransactionId request (Mandatory parameter for MPRAPI PaymentService) The target payment service. The Initial Authorization Reference received from the payment service. The amount to be voided in the lowest monetary unit. A unique identifier to identify the transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The Initial Authorization Reference received from the payment service. The amount voided in the lowest monetary unit. The transaction status (Success or Fail) The transaction result code. A unique identifier to identify the merchant's payment profile. A unique identifier to identify the transaction. A unique identifier to identify a preceding transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The transaction order or reference number. The Master Pass Remote API transaction id that was returned on the generateTransactionId request (Mandatory parameter for MPRAPI PaymentService) The card details. The Master Pass Remote API endpoint to POST the payload to i.e. v3/purchaseTransactionId The JSON payload to be posted the the MPRAPI endpoint i.e. A unique identifier to identify the transaction. The transaction timestamp. A unique sale identifier for reconciliation purposes. A unique identifier for reconciliation purposes. The transaction status (Success or Fail) The transaction result code. A unique identifier provided by the merchant on the API call to identify the transaction. A unique identifier to link split payments Merchant GUID. A unique identifier for reconciliation purposes. The transaction timestamp. The target payment service must always be eBucks. The transaction order or reference number. The total amount in cents e.g. the amount R25.95 must be written in cents as 2595. Minimum amount is 10 cents (1 eBuck) and maximum amount is 99999990 cents. This is the URL that the system will redirect to after a successful eBucks payment is completed. The merchant needs to implement this controller. The URL the system will redirect to if the customer chooses to cancel before completing payment. The merchant needs to implement this controller. The ReturnURL will be used if the CancelURL is not defined. The customer email. The customer first name. The customer last name. A unique identifier for reconciliation purposes. A unique identifier to identify the transaction. A unique identifier to link split payments The transaction timestamp. The transaction status (Success or Fail) The unique eBucks session token relating to this payment. The transaction result code. Merchant GUID. A unique identifier provided by the merchant on the API call to identify the transaction. A unique identifier to link split payments The unique eBucks session token relating to this payment. Either the eBucksToken or the PreviousTransactionID must be provided A unique identifier for reconciliation purposes. A unique identifier to identify the transaction. A unique identifier to link split payments The transaction timestamp. The transaction order or reference number. The unique Token relating to this payment. The total ZAR amount in cents supplied by the merchant. The total ZAR amount in cents authorized to be paid in eBucks. The date and time at which this authorization expires. The transaction status (Success or Fail) The transaction result code. The ecentricswitch service contract. The Payment method attempts to process a payment transaction with a single call. The method essentially combines the Authorize and Capture in a single transaction.

The CreateMasterPassTransaction method generates a token/QR code that can be used to make a payment via mobile phone

The AddCard method stores the card details against a merchant user id and provides a token that can be used to transact using the Secure3DLookup, Authorize, Capture, Void and Payment methods

The ListUserCards method lists the card details stored against a merchant user id

The ListMerchantCards method lists the card details stored against a merchant id

The ListMerchantCards method removes the card details stored against a merchant user id

The Authorize method attempts a funds reservation against the provided card details.

The Capture method requests the settlement of the funds reserved through an Authorize transaction.

The Refund method allows the merchant to issue a refund (full or partial) of a Capture or Payment transaction.

The Void method releases the funds reserved through the Authorize transaction.

The Secure3DLookup method allows merchants to authenticate cards through 3D Secure.

The MPRAPI method passes the Master Pass Remote API request through to masterpass, and inserts the card number into the payload.

The pre Authorize method attempts incremental funds reservation against the provided card details.

The Pre Auth Void method releases part of the funds reserved through the Authorize transaction.

In order to create an eBucks payment, one needs to trigger CreateEbucksPayment method.

Triggered to verify an eBucks transaction. It is merely an information request.