The problem we help solve
A clearer handoff. Less uncertainty.
An authorisation is treated as a completed sale, while capture failures, cancellations and refunds appear later in a separate operational queue.
How BrownBag helps
We map Adyen payment outcomes to the states your order and finance systems actually need. The implementation can use the appropriate Sessions or advanced flow, with the payment methods approved for your account.
From requirement to operation
Your Adyen workflow
Design the payment states
Agree when to authorise and capture, how inventory is reserved and what should happen when a payment stays pending.
Implement the supported flow
Connect the chosen checkout components and server-side integration, including the required authentication steps and webhook processing.
Reconcile the exceptions
Test capture, cancellation and refund paths. Give operations clear references and an escalation process for incomplete or failed transactions.
What we can deliver
- Authorisation and capture workflow
- Checkout and notification integration
- Payment exception and finance handover
We agree the systems, responsibilities, acceptance checks and support arrangements before implementation begins.
Define the right scope
Adyen onboarding and available payment methods depend on your entity, market and contract. Acquiring, platform payouts and advanced products require their own approval and scope.
Provider requirements and interfaces can change. We recheck the applicable documentation and account access when scoping your project.
Official Adyen reference →Your questions, answered
Can payment capture wait until we are ready to dispatch?
We can evaluate a separate authorisation/capture workflow where your payment methods and agreement support it. Capture timing and expiry limits must be agreed before changing fulfilment behaviour.
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.