Mambu Payment Gateway

The purpose of Payment Order capability is to orchestrate the movement of money between an account in Mambu and an account at a third-party financial institution (both domestic as well as international).

The orchestration includes triggering Payment Execution on the user-specified date, debiting / crediting the account in Mambu (i.e. calling transaction API), storing-and-forwarding the credit / debit instruction for settlement in a third party financial institution via the Mambu Payment Gateway (MPG), that in turn sends it out to Payment Network.

The tools needed to operate the payments functionality are:

• Mambu UI
• API development environment (e.g Postman)
• Mambu Payment Gateway UI

Logging in

Depending on the level of security enabled for your instance you will either log in using regular authentication using just a username and password or multi-factor authentication (MFA) where a one time passcode is sent to a mobile phone number associated with your account. For more information, see User Administration and Audit Trail - Multi-factor authentication.

Navigation menu

The navigation menu is located on the left of the page. The navigation menu gives access to the following sections:

• Incoming - Payment messages received (e.g Payments received from the financial network)
• Outgoing - Payment messages received (e.g Payments sent to the financial network)
• Pending - Payment messages that require manual intervention of PG users
• Configuration - System configurations such as Tenant BIC, AML enabling
• Security - Users management and audit trail

Incoming / Outgoing

The incoming / outgoing menus are used to monitor received/sent payment messages. When clicking this menu, the user is prompted with two sub-menus:

• SEPA
• Alerts

The sub-menu SEPA gives users a view on the incoming / outgoing SEPA messages:

Transactions List

Each row represents one of the following SEPA messages:

• Pacs.008
• Pacs.004
• Pacs.002
• Camt.056
• Camt.029

The list provides the following information on a message:

• System ID
• Message type
• Message ID
• Number of transactions inside a given message
• Settlement date

Clicking a single row will provide users more information on the payment message:

• Transaction number
• Message ID
• Status
• Amount
• Creditor IBAN

By clicking on the arrow of each row the SEPA message (xml) will be seen in full on the detail screen.

The fields displayed are relevant for the end users and provide useful information in case of investigation or customer requests.

List row detail

Clicking a single row will redirect users to the full details of the payment message:

The image above represents a SEPA message (xml) and can be seen in full in this detail screen. For more information, please refer to the European Payments Council's 2019 SEPA Credit Transfer rulebook version 1.2.

The fields displayed are relevant for the end users and provide useful information in case of investigation or customer requests

Alerts

The sub-menu Alerts, gives users a list of alerts for the SEPA messages. The section provides information on the error so that the user can trigger actions to resolve the issue.

The alerts section can be found both on the outgoing and incoming menus.

Pending

In this section you will see messages that are pending to be sent: either they require manual input before they can proceed the payment flow, such as outgoing returns requests or replying to these return requests positivily or negativily or messages that cannot be sent given the day the messages were generated is a holiday.

Outgoing returns waiting to be accepted or rejected:

Pending pacs.008 given a payment was sent on an holiday

Gateway Status

Compliance checks

Incoming AML

Incoming Anti-money laundering (AML) allows banks and other financial institutions to send incoming payment details to the external third party AML provider (AML TPP) so that they can reduce the risk of money laundering with a frictionless flow in the Mambu Payment Gateway.

The MPG sends the transactions details and holds the payment process until it gets an AML result to the payments sent. The screening of a payment on the AML TPP can generate three types of results:

• Accepted: No flags were raised on the AML TPP and payment can proceed the flow - crediting the beneficiary.
• Suspended: Some flags were raised on the AML TPP and further analysis is being run on the AML TPP. The payment must be on hold until either an accepted or rejected is received.
• Rejected: Payment was tagged on the AML TPP with a AML flag that lead to a rejection. The payment flow is stopped and the beneficiary is not credited.

Send payment details

	<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.02">
   <FIToFICstmrCdtTrf>
      <GrpHdr>
         <MsgId>AML1</MsgId>
         <CreDtTm>2020-01-02T10:40:13</CreDtTm>
         <NbOfTxs>1</NbOfTxs>
         <TtlIntrBkSttlmAmt Ccy="EUR">1</TtlIntrBkSttlmAmt>
         <IntrBkSttlmDt>2020-01-02</IntrBkSttlmDt>
         <SttlmInf>
            <SttlmMtd>CLRG</SttlmMtd>
            <ClrSys>
               <Prtry>ST2</Prtry>
            </ClrSys>
         </SttlmInf>
         <InstgAgt>
            <FinInstnId>
               <BIC>CECAESMMXXX</BIC>
            </FinInstnId>
         </InstgAgt>
         <InstdAgt>
            <FinInstnId>
               <BIC>BTRLRO22</BIC>
            </FinInstnId>
         </InstdAgt>
      </GrpHdr>
      <CdtTrfTxInf>
         <PmtId>
            <InstrId>NOT1</InstrId>
            <EndToEndId>NOT1</EndToEndId>
            <TxId>NOT1</TxId>
         </PmtId>
         <PmtTpInf>
            <SvcLvl>
               <Cd>SEPA</Cd>
            </SvcLvl>
         </PmtTpInf>
         <IntrBkSttlmAmt Ccy="EUR">1</IntrBkSttlmAmt>
         <ChrgBr>SLEV</ChrgBr>
         <Dbtr>
            <Nm>Jane Doe</Nm>
            <PstlAdr>
               <Ctry>ES</Ctry>
            </PstlAdr>
            <Id>
               <OrgId>
                  <Othr>
                     <Id>GFA</Id>
                  </Othr>
               </OrgId>
            </Id>
         </Dbtr>
         <DbtrAcct>
            <Id>
               <IBAN>RO10INGBCBN4EVKASDJ8YNGT</IBAN>
            </Id>
         </DbtrAcct>
         <DbtrAgt>
            <FinInstnId>
               <BIC>CECAESMMXXX</BIC>
            </FinInstnId>
         </DbtrAgt>
         <CdtrAgt>
            <FinInstnId>
               <BIC>BTRLRO22</BIC>
            </FinInstnId>
         </CdtrAgt>
         <Cdtr>
            <Nm>John Doe</Nm>
            <PstlAdr>
               <Ctry>ES</Ctry>
            </PstlAdr>
            <Id>
               <OrgId>
                  <Othr>
                     <Id>V94025590</Id>
                  </Othr>
               </OrgId>
            </Id>
         </Cdtr>
         <CdtrAcct>
            <Id>
               <IBAN>RO71BTRLV67M9G4ASDEJ5D2</IBAN>
            </Id>
         </CdtrAcct>
         <RmtInf>
            <Ustrd>Incoming Payment</Ustrd>
         </RmtInf>
      </CdtTrfTxInf>
   </FIToFICstmrCdtTrf>
</Document>

processAmlResponse

Accepts AML check results for Payment Orders.

{
  "groupHeader": {
    "messageIdentification": "SCTORD200020190305ORD000011122"
  },
  "transactions": [
    {
      "status": "Accepted",
      "paymentIdentification": {
        "transactionIdentification": "00730100631BHGCSDW"
      },
      "debtorAgent": {
        "institutionIdentification": {
          "bicfi": "BTCLYU23"
        }
      },
      "interbankSettlementDate": "2019-06-28T00:00:00.000Z"
    }
  ]
}

Responses