Paymentology Integration
  • 16 May 2024
  • 4 Minutes To Read
  • Dark
    Light
  • PDF

Paymentology Integration

  • Dark
    Light
  • PDF

Article summary

Early Access Feature
If you would like to request early access to this feature, please get in touch with your Mambu Customer Success Manager to discuss your requirements. For more information, see Mambu Release Cycle - Feature Release Status.

We partner with Paymentology to provide card issuing and processing services. Paymentology is a card issuing platform providing an Open API. The Paymentology connector is for Mambu customers who want to offer debit cards to their clients. Using the Paymentology connector means you do not need to build out your own gateways or deal with messaging standards such as ISO 8583.

Paymentolgy works globally and is integrated with the Visa, Mastercard, and MADA networks - allowing you or your clients to make the best choice of a card product. For more information about Paymentolgy see Mambu Marketplace or the Paymentology website.

The Mambu-Paymentology integration connects the Mambu banking platform and Paymentology payment card processing centre. The integration focuses on processing payment card authorization requests and clearing transactions as well as a list of various related messages, such as advices and reversals. Mambu is where the card account's available and ledger balance are maintained.

Prerequisites

Before working with cards, make sure you have your Mambu environment set up. There may be additional setup to be done in Paymentology if you intend to use their simulation workplace for the testing purposes.

Architecture

The Mambu-Paymentology integration is based on the Fast and Secure Transactions (FAST) message interface. Communication is done using two endpoints, to which Paymentology forwards payment card authorization and transaction messages, received from the network, and converted into the FAST v3 format. The received messages are mapped to the corresponding Mambu APIs, which are called in order to update the available and ledger balances of a Mambu payment card account.

The first endpoint is dedicated to payment card authorization related messages, such as authorization requests, balances inquiries, various reversals, and advices. The full list of supported authorization messages is provided in Authorizations endpoint.

The second endpoint is dedicated to process debit and credit settlement transactions as well as transaction reversals. More details in Transactions endpoint.

Currently the scope of the integration is limited to authorizations and card transactions coming from the Mastercard scheme. Accordingly the following cardholder transaction type codes are supported:

Processing codeDescriptionDirection
00PurchaseDebit
01WithdrawalDebit
02Debit AdjustmentDebit
09Purchase with Cash BackDebit
10Account FundingDebit
17Cash DisbursementDebit
18Scrip issueDebit
20Purchase Return
Refund
Credit
21DepositCredit
22Credit AdjustmentCredit
23Check Deposit GuaranteeCredit
24Check DepositCredit
28Payment TransactionCredit
30Balance inquiryNone

Authorizations endpoint

The authorizations endpoint is dedicated to authorization processing. Authorization messages are checked for mandatory fields and processing codes are checked to ensure that they are supported. If the checks are passed, a corresponding Mambu API is called. The 200 OK is returned with ISO8583 response fields, after receiving a response from Mambu. The response includes field DE39 Response Code with the defined ISO8583 response code, which is returned back to the Acquirer as a result of the authorization processing. If the checks are not passed, the 400 Bad Request is returned along with the error reason.

The following authorization messages are supported:

Business caseMTIDE3_1Purpose
Debit authorization request010000, 01, 02, 09, 10, 17, 18Create a debit hold if the available balance is sufficient.
Credit authorization request010020, 21, 22, 23, 24, 28Create a credit hold.
Incremental authorization request010000, 01, 02, 09, 10, 17, 18Increase a debit hold amount if the available balance is sufficient.
Balance inquiry010030Get the ledger and the available balances of a card account.
Debit authorization advice012000, 01, 02, 09, 10, 17, 18Create a debit hold without the available balance check.
Credit authorization advice012020, 21, 22, 23, 24, 28Create a credit hold.
Incremental authorization advice012000, 01, 02, 09, 10, 17, 18Increase a debit hold amount without the available balance check.
Final authorization advice012000, 01, 02, 09, 10, 17, 18Change a debit hold amount.
Declined authorization advice0120-Fully reverse a hold.
Declined incremental authorization advice0120-Reverse the increase of a hold.
Full authorization reversal0400, 0420-Fully reverse a hold
Partial authorization reversal0400, 0420-Partially reverse a hold.
Debit transaction request020000, 01, 02, 09, 10, 17, 18Create a debit transaction if the available balance is sufficient.
Credit transaction request020020, 21, 22, 23, 24, 28Create a credit transaction.
Debit transaction advice022000, 01, 02, 09, 10, 17, 18Create a debit transaction without the available balance check.
Credit transaction advice022020, 21, 22, 23, 24, 28Create a credit transaction.
Declined transaction advice0220-Fully reverse a transaction.
Transaction reversal0400, 0420-Fully reverse a transaction.
Declined request0100, 0200-Decline authorization or transaction request.

Transactions endpoint

The transactions endpoint is used to process settlement transactions. Each card transaction from the Mastercard file is converted to an API call by Paymentology. Transaction messages are checked for mandatory fields and processing codes are checked to ensure that they are supported. If the checks are passed, a corresponding Mambu API is called. The 200 OK is returned in case a card transaction is successfully processed by Mambu. If the checks are not passed, the 400 Bad Request is returned along with the error reason.

The following transaction messages are supported:

Business caseMTIISO_MSG.3Purpose
Debit transaction presentment124000, 01, 02, 09, 10, 17, 18Create a debit transaction without the available balance check.
Credit transaction presentment124020, 21, 22, 23, 24, 28Create a credit transaction.
Presentment reversal1240-Fully reverse a transaction.

Was this article helpful?