back-office/ERP Integration (Async API)

Best for: back-office systems, ERP platforms, manual order entry workflows

Overview

The Async API enables payment processing for back-office systems, ERP platforms, and manual order entry workflows where buyers authorize orders outside the checkout flow.

Use this integration when:

• Orders are created manually or imported from external systems
• Real-time buyer interaction during checkout is not possible
• You need to process B2B payments asynchronously

Supported payment methods:

• Invoice
• SEPA Direct Debit
• Installments
• Billing Statement (requires buyer onboarding via Digital Trade Account)

Implementation steps:

• Create orders via Create Async Order endpoint
• Request Payload must include complete buyer information for identification
• Buyer authorization happens asynchronously via email, not in real-time during checkout
• Buyer authorization changes the status of the order from authorized to confirm
• Check Async Order Status article and map relevant Mondu statues in your system
• Register Webhooks topic Order to receive the order status updates authorized, pending, confirm, declined
• Invoice template must comply with Mondu's legal requirements. See Mondu Invoice Snippet for details
• Submit PDF Invoice via Create Invoice endpoint. The order must be in status confirmed
• Key Difference: Confirm Order is not required
• Follow this guideline Required Integration Components to complete the integration

❗️

In case you submit legal_form_category: einzelunternehmen be aware that the owner-object with the attributes: first_name, last_name and birth_date will be required.

Mondu API (async version)

API Integration to cover all steps of your order life cycle.

Customer order authorization

Using the Async Order API, a customer does not place an order in the checkout and is not redirected to a Mondu interface where the customer agrees to Mondu's payment agreement. Legally, we still need to ensure that the customer confirms Mondu's payment agreements to process orders from the buyer.

To ensure this, we offer 2 solutions:

Via email after placing the order

• After creation of the order via API and approval by Mondu, your customer will receive an email from Mondu to authorize the order.
• Within the email, we send a link which opens a page hosted by Mondu presenting the order and payment details to the customer.
• The customer has to confirm the order and by doing so also agrees to our payment terms.
• After successful authorization by the customer, the order transitions to the authorized state. Mondu then transitions the order to confirmed and invoices can be issued for the order.
• In case the customer does not authorize the order, we send a reminder email after 2 and 5 days.
• The confirmation link expires after 30 days.
• Mondu sends the order authorization link in the webhooks order/authorized

Via buyer hosted onboarding

• Mondu offers the option to onboard your customers before any purchases - using the Hosted Buyer Onboarding.
• We ask your customer to confirm Mondu's payment agreement during the buyer onboarding.
• Once a buyer has been onboarded and approved by Mondu, no additional customer authorization at the individual order level is required.