The problem we help solve
A clearer handoff. Less uncertainty.
A shopper approves a PayPal payment, but the store treats that approval as a completed capture. Cancelled journeys, delayed events and dashboard refunds then leave order and finance records out of step.
How BrownBag helps
We scope PayPal checkout around your eligible business account and storefront. The implementation connects the supported PayPal JavaScript SDK with server-side Orders API operations, then maps the resulting order and capture references to fulfilment and support.
From requirement to operation
Your PayPal workflow
Confirm account eligibility and the buying journey
Review the business account country, receiving capabilities, currencies and enabled checkout products. Choose immediate capture or an authorise-then-capture workflow around how you confirm and fulfil orders. Keep optional card, wallet and recurring products within their approved scope.
Connect approval, capture and verified events
Create and capture the PayPal order through your server, validating the amount and currency against your own order record. Handle verified webhooks for the correct app with duplicate-event protection, keeping buyer approval separate from completed payment.
Test customer and back-office outcomes
Exercise cancellation, declined funding, interrupted returns and duplicate notifications in the sandbox. Test supported refunds or voids, preserve order and capture references, and document how staff investigate payment exceptions and reconcile records.
What we can deliver
- Account-specific PayPal checkout and capture design
- Server-side order mapping and verified webhook handling
- Sandbox journey tests and refund/reconciliation handover
We agree the systems, responsibilities, acceptance checks and support arrangements before implementation begins.
Define the right scope
PayPal availability and receiving features depend on the business account country, approved product and current provider rules. We verify eligibility before promising an integration and do not claim Pakistan merchant onboarding. Subscriptions, saved payment methods, marketplace payouts and advanced card products require separate approval and scope. This service is distinct from Braintree integration.
Provider requirements and interfaces can change. We recheck the applicable documentation and account access when scoping your project.
Official PayPal reference →Your questions, answered
Is approving a PayPal order the same as completing payment?
No. Buyer approval allows the next payment action, while capture completes the charge. We define the order-release rule around the verified capture state or the separately agreed authorisation workflow, so a return to the store is not treated as proof of payment.
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.