Payment request
Design the purchase path
DEVELOPERS
Start with the payment flow, then write the integration.
Map the payment request, checkout handoff, and final outcome before connecting an API. Include the customer who leaves midway and the attempt that needs a retry.
Let's talkAPI / FLOW
Plan the handoff from order to payment
Decide when checkout starts, how the result reaches your system, and what a customer sees if a payment fails.
Checkout handoff
Introduce checkout at the right moment
Outcome in your system
Show a clear conclusion
This page is a product overview. Verified API endpoints and production credentials are not yet published.
Make the checkout feel native
An API route is useful when a purchase already happens in your own site or application. Decide where payment should appear in that journey and how the customer returns to the order they recognise. An integration should support the experience, not interrupt it.
Design for the person behind the order
Show what the customer is paying for and what happens after submission. A declined payment, an abandoned checkout, and a completed order need different messages. Your internal order record should reflect those distinctions as clearly as the screen does.
Give the team a working model
Map the fields your team needs to fulfil the sale, then agree how payment outcomes reach those records. Keep the order and its payment result readable to the people who fulfil it.
MANUELL
Tell us how you sell.
We can discuss the payment route that fits your website, sales conversations, or online store.
Let's talk