Connect commercetools with MaldoPay to support secure card payments, reduce checkout friction, and keep payment data clean for reporting and reconciliations.
• Checkout creates a commercetools Payment object that stores MaldoPay transaction references, payment method metadata, and amount details per currency.
• Authorization, capture, void, refund, and chargeback events are received via MaldoPay webhooks and mapped to commercetools payment transactions with state transitions.
• Order state and payment state in commercetools are updated based on validated MaldoPay event types, amounts, and idempotency keys to prevent duplicate processing.
• Partial captures and partial refunds are represented as separate commercetools transaction entries, preserving an auditable timeline per order.
• Failures and mismatches are logged with correlation IDs across MaldoPay and commercetools to support reconciliation and support workflows.
• Customer payment redirects or tokenized flows are handled by passing session identifiers between storefront, MaldoPay, and commercetools, keeping PCI-sensitive data out of commercetools.
.png)
We map MaldoPay payment events to commercetools Payments and Orders, then implement secure webhooks to keep auth, capture, and refund statuses consistent end to end.
Transaction IDs, payment status, amounts, currency, partial captures, refunds, and failure reasons are synced so finance can reconcile orders without manual cross-checking.
Yes. We model captures and refunds at transaction level, so you can capture per shipment or line group while keeping a clean order payment history.
We ingest dispute status updates via webhooks and write them to commercetools so support and finance can track cases against the correct order and payment record.
Yes, with per-project or per-store configuration for currencies, payment methods, and settlement rules, plus region-aware routing where needed.




