PAYMENT INTEGRATIONS
Payment experiences built around your business model
Payments are more than a checkout screen. They involve transaction states, order or booking logic, notifications and the handling of successful and unsuccessful outcomes. We integrate payment services into web platforms so the surrounding workflows behave consistently with your business requirements.
Selected work
Payment workflows for different platform models
Butterply
A home-services booking platform connecting a booking workflow with payments, escrow integration, messaging and notifications.
Canada · 2023Evergreen Earth
A forest-restoration nonprofit website featuring donations and donor accounts.
USA
These projects represent different transaction contexts: service bookings and nonprofit contributions. The integration approach must reflect the requirements of the platform and the capabilities of the relevant payment provider.
How it works
Connect the transaction to the complete workflow
Define the payment journey
We map the process from the initial booking, order or donation through to payment confirmation and the next business action.
The path from booking or order to confirmation and the next action.
Select the integration approach
We assess the payment provider, API capabilities, platform requirements and supported transaction flows.
A provider and API approach that supports your transaction flows.
Integrate the system
We implement the required payment connections and connect transaction events to the relevant platform logic and notifications.
Payments connected, with each event wired to platform logic.
Test transaction scenarios
We test agreed success and failure paths, relevant status changes and the surrounding communication workflows before launch.
Success and failure paths, status changes and messages tested.
What’s included
The payment flow and the systems around it
Keep transactions and the workflows around them in sync.
Gateways, escrow and the flows around them.
- 01
Payment gateway integration
Connect a supported payment service to your platform and implement the API interactions required by the agreed transaction flow.
- 02
Booking and marketplace payments
Integrate payments into booking or marketplace workflows, connecting relevant payment events with the status of the associated order or booking.
- 03
Escrow integration
Where an appropriate provider and supported flow are available, integrate escrow-related functionality into the platform’s transaction process.
- 04
Transaction-state handling
Define how the application responds to relevant transaction states, including successful, unsuccessful, pending or otherwise unresolved payments where supported by the provider.
- 05
Notifications and messaging
Connect relevant payment events to confirmation messages, email notifications or other agreed communication channels.
- 06
End-to-end testing
Test the agreed transaction journeys and their associated application behaviour, including relevant failure scenarios, before deployment.
FAQ
Common questions
Which payment gateways can you integrate?
The suitable provider depends on your business location, target customers, transaction model and platform requirements. We assess the available APIs and provider requirements before confirming the integration scope.
Who pays the gateway and transaction fees?
Payment processing fees, provider subscriptions and other third-party charges are separate costs unless explicitly stated otherwise. Relevant costs are identified in the quotation.
Can you integrate escrow into a marketplace?
We can assess and implement a supported escrow-related workflow where an appropriate provider and integration are available. The scope depends on the provider’s capabilities, the platform’s transaction model and applicable requirements.
Do you test unsuccessful payments as well as successful ones?
Yes. The agreed test plan should include applicable failure paths and relevant transaction-state changes, not just a successful checkout. The specific scenarios depend on the provider and the integration.
Does the integration cover regulatory and compliance requirements?
The integration must account for applicable provider requirements and the responsibilities of the business operating the platform. We define the technical scope around the selected provider and intended transaction flow; legal, financial and regulatory obligations must be assessed for the specific business and jurisdiction.