The problem we help solve
A clearer handoff. Less uncertainty.
Customers can return before a payment notification reaches the store. If order status depends on that return alone, staff may see an unpaid order while the customer believes the transaction is complete.
How BrownBag helps
We scope a supported Mollie plugin or Payments API integration around your eligible business account and storefront. The result is a connected checkout journey with a clear handoff between buyer, payment provider and order operations.
From requirement to operation
Your Mollie workflow
Select the account and checkout approach
Confirm the business profile, activated methods and checkout currencies. Review your platform plugin or a custom Payments API flow. Agree how buyers choose a method and how the store handles pending payments before reserving stock or sending confirmation.
Connect payment creation and status retrieval
Store the Mollie payment ID against the order and send the customer to the returned checkout URL. Use the webhook as a prompt to retrieve the payment through the API, then apply the verified state. Keep customer-facing status aligned with the order record when notifications arrive later.
Rehearse refunds and operational recovery
Test paid, failed, expired and cancelled outcomes with the applicable test setup. Check repeated notifications and customers closing their browser. Define the refund workflow and reference trail, then give staff a concise process for investigating payment, order and settlement discrepancies.
What we can deliver
- Profile, method and integration-route specification
- Payment-ID mapping and API-verified status workflow
- Test evidence and refund/reconciliation operating notes
We agree the systems, responsibilities, acceptance checks and support arrangements before implementation begins.
Define the right scope
Mollie determines eligible business countries, account approval and method activation. Customer payment-method availability is not a promise of merchant eligibility. Recurring payments, marketplace onboarding through Mollie Connect and in-person payments are scoped separately from store checkout.
Provider requirements and interfaces can change. We recheck the applicable documentation and account access when scoping your project.
Official Mollie reference →Your questions, answered
How should the store handle a customer returning before the webhook arrives?
Display the stored payment state and retrieve the latest verified status when appropriate. Keep the order pending until payment is confirmed, and make repeated updates safe so a later webhook cannot send a second fulfilment instruction.
What should we include in the first brief?
Share your current store and systems, provider account status, target markets and the workflow you want to improve. Include typical volumes and the person responsible for operations. Do not send passwords, API keys or customer records.