Payments using the Mirakl connector
We categorise payment methods into seven families. Each family has similar features, a single integration, and common checkout experiences.
You can use one of our existing connectors or build your own integration to accept payments.
Note
When implementing payments, don’t use any of the Connect charge types. The connector takes care of splitting the funds based on your Mirakl orders.
Payment creation![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
Choose the payment method families according to the order workflow most adapted to your use case.
Family | Pay on acceptance | Pay on delivery | Pay on due date |
---|---|---|---|
Cards | |||
Bank debits | |||
Bank redirects | |||
Credit transfers | |||
Buy now, pay later | |||
Vouchers | |||
Wallets |
Below are some additional guidelines for adapting your payment integration to your workflows.
Pay on acceptance![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
For cards, set the value of capture_method option to manual
when completing the PaymentIntent to authorise only. The connector captures the funds automatically as soon as all sellers have accepted or refused their respective orders. The orders must be accepted or refused within 7 days, the validity period of an authorisation.
Because the payment confirmation is immediate for bank redirects, wallets and buy now, pay later, we recommend setting up your orders to be accepted automatically and using refunds when sellers can’t fulfill their order.
Pay on delivery![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
For cards, you can authorise only during checkout if you have business rules in place to capture the payment within 7 days. Otherwise, save the card at checkout and authorise later.
For bank debits, you can save the bank account at checkout and initiate the payment after the seller accepts their order.
Pay on due date![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
You can use Stripe Billing to send an invoice to your customers who can then pay using our hosted invoice page.
Payment validation![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
To handle the payment validation of your Mirakl orders, you can rely on the built-in job or call the PA01 API yourself if you have specific needs such as offering coupons.
To enable the built-in job, you have to first map the Mirakl order with the successful Charge by updating the metadata:
curl https://api.stripe.com/v1/charges/ch_1Hmloy2eZvKYlo2C2Tx3W00V \ -u
: \ -d "metadata[mirakl_commercial_order_id]"=123sk_test_4eC39HqLyjWDarjtT1zdp7dc
The workflow starts when a seller accepts their logistic order.
- The payment validation job fetches newly accepted Mirakl orders.
- The connector validates the payment in Mirakl.
- For cards, the payment is captured when all the logistic orders are accepted or refused.
Payment split![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
The workflow starts when the payment is validated on Mirakl and captured on Stripe.
- The payment split job fetches newly validated Mirakl orders.
- The connector transfers the order amount to the seller after deducting your commission.
Payment refund![](https://b.stripecdn.com/docs-statics-srv/assets/fcc3a1c24df6fcffface6110ca4963de.svg)
The workflow starts when you request a refund on a Mirakl order.
- The payment refund job fetches newly refunded Mirakl orders.
- The connector creates a refund on Stripe, validates the refund on Mirakl, and then reverses the transfer used to split the payment.