This guide provides a comprehensive overview of the integration steps required to implement
Mondu Payment Methods in your system. Follow these steps to integrate, test, and deploy Mondu's payment solution.

1. Obtain API Credentials

Apply for a Mondu account by contacting [email protected]
Receive your Demo API Key at the start of onboarding
Receive your Production API Key after your integration passes review

Timeline: Demo credentials are typically provided within 1-2 business days. Production credentials are issued after integration validation.

2 Required Implementation Components

Create Order Flow

Merchant system has to send the buyer data and information about the products to Mondu Risk & Fraud Engine to identify the buyer and evaluate the transaction. Depending on the type of the system (E-Commerce, Back-office, ERP), it can be done through different endpoints. Read this section (Implement a suitable order creation flow) to choose an order creation flow suitable to your system.

Confirm Order

When the order was successfully placed in the shop system and the shop system received the order/authorized webhook trigger Confirm Order Request to change the status of the order in Mondu system form authorized to confirmed.

Webhooks Handling

Make sure that the Mondu servers can reach the webhook endpoints. Mondu communicates changes to the status of the resources (Order, Factoring, Invoice, Buyer, Payout) through webhooks; therefore it is important that you enable your system to receive webhooks attempts by whitelisting Mondu IP addresses and register for relevant webhook topics.

Pending State

To increase the order approval rate, Mondu can set some orders to manually review the order within the timeframe of 24 business hours. When the order is in manual review, it has status pending. The result of manual review will be communicated to the merchant system via the order webhooks topic. Please read this article (Implement Pending) for more details.

Create Invoice

Mondu can make a payout to the merchant's bank account only, if the invoice PDF is sent to Mondu via the Create Invoice endpoint. The invoice should be sent to Mondu when the order in merchant's system is set to shipped and the order in the Mondu system has status confirmed (Order Status, Async Order Status).

It is possible to submit multiple invoices for one order until the sum of partial invoices will be equal to total order amount.

Create Credit Notes

If the part of shipped order was returned, or it was discounted, sent to Mondu Create Credit Note request to adjust the invoice amount.

Order Adjustments

Order can be adjusted through Adjust Order Request in case the buyer asked to change the original order or costs related to the order changed before the products were shipped to the buyer.

The information about the buyer cannot be changed.

The addition of products or the increase order related costs may trigger another round of risk assessment. In this case the status of the order will be set to pending until Mondu will review adjusted order. You will be updated about the change of the status of the order through webhooks.

Cancel Operations

If any of the order, invoice, credit notes get cancelled in merchant's system, send this information to Mondu via relevant endpoint:

3 Implement a suitable order creation flow

The system you use to create orders will determine the endpoint you will use to create order in Mondu system (Create Order, Create Async Order) and integration type (API vs Plugin).

Integration in Shop via direct API implementation:
- Recommended for checkouts in e-commerce platforms
- Enables the following payment methods:
  - Invoice, SEPA-Direct Debit, Instalments, PayNow
  - Consolidated Statement requires that the buyer is onboarded via Digital Trade Account
- Order hast to be created via Create Order endpoint
- Order requires buyer authorization via Mondu Hosted Checkout Page
- Requires confirmation from shop system via Confirm Order
Integration in Backoffice via API implementation (Create Async Order):
- Enables the following payment methods:
  - Invoice, SEPA-Direct Debit, Instalments
  - Consolidated Statement requires that the buyer is onboarded via Digital Trade Account
- Recommended for shop back offices and ERP
- Order has to be created via Create Async Order
- Order has to be confirmed by the buyer via e-mail
Integration in Shop via E-Commerce Plugin:
- Recommended for checkouts in e-commerce platforms
- Enables the following payment methods:
  - Invoice, SEPA-Direct Debit, Instalments, PayNow
  - Consolidated Statement requires plugin customization to support buyer is onboarded via Digital Trade Account
- Order requires buyer authorization via Mondu Hosted Checkout Page

4 Test using recommended e-mail

Mondu defined on DEMO system e-mail patterns that trigger specific risk engine outcome for testing purposes.

Use the following e-mail patterns to test order creation flow:

Order creation

Order Flow	E-Mail Pattern	Use Case
Approved Order Flow	[email protected]	If you use this e-mail, the orders will always be accepted in the order creation flow.
Pending Order Flow	[email protected]	If you use this e-mail, the orders will always be set to pending in the order creation flow.
Declined Order Flow	[email protected]	If you use this e-mail, the orders will always be declined in the order creation flow.

Buyer onboarding (Onboard Buyer / Digital Trade Account)

Use the following e-mail patterns to the buyer onboarding flow:

Onbord Buyer / Digital Trade Account

Digital Trade Account	E-Mail Pattern	Use Case
Approved Order Flow	[email protected]	If you use this e-mail, the buyer will be approved in the buyer onboarding process and his orders will always be accepted in the order creation flow.
Pending Order Flow	[email protected]	If you use this e-mail, the buyer will get status pending in the buyer onboarding process and his orders will always be set to pending in the order creation flow.
Declined Order Flow	[email protected]	If you use this e-mail, the buyer be declined status in the buyer onboarding process and his orders will always be declined.