Payments linked to your product
Keep your application reference with the payment request. Your own backend controls which purchase or user record the payment belongs to.
Solutions / ApplicationsPAYMENTS INSIDE YOUR PRODUCTConnect payments
Connect payments
to the right user.
Build a payment journey around your application’s own users and orders. Use checkout for a purchase, or API-created custody accounts when you need to review ongoing account activity.
BUILT FOR APPLICATIONS
Choose the payment model your application needs
A single purchase and an ongoing user account need different payment models. An order-based checkout connects a payment to a purchase. Custody connects API-created users, payment requests and transaction history for applications that need an account view. Your application creates those records; the dashboard gives your team a place to inspect them.
API-created account activity
Create custody users and their payments through your integration. Review balances, requests and transactions in the dashboard without manually creating users.
An operational view for your team
Use the merchant workspace to investigate a user’s payment history and request status. Keep the application’s access rules in your own backend.
FROM SETUP TO CONFIRMATION
A practical path to your first payment.
Start with the payment model that fits your business. Connect the right records, guide your customers and follow the confirmed result.
- 01
Choose checkout or custody
Use checkout for discrete purchases. Use custody when your product needs users with a continuing payment history.
- 02
Connect from your backend
Set up merchant API credentials and create the appropriate records from your application server. Keep secret credentials out of client-side code.
- 03
Reconcile payment activity
Verify payment results before granting access or updating application balances. Review the related user and transaction records in the dashboard.
PUT IT TO WORK
Where this solution fits.
Paid application features
Connect a one-time payment to an upgrade or a specific purchase.
Account-based products
Use API-created custody records to review activity for individual users.
Internal support tools
Find the request and transaction associated with a customer’s support enquiry.
BEFORE YOU STARTYour questions,
Your questions,
answered.
Understand the payment flow and the role of your business before choosing an integration.
Discuss your requirementsAre custody users created in the dashboard?
No. Your application creates custody users and payments through the API. The dashboard is used to list, inspect and review them.
Should every application use custody?
No. If each payment belongs to a separate purchase, an order checkout may be the clearer option. Choose custody when your application needs ongoing user-account records.
Where should API credentials be stored?
Keep secret credentials on your application server. The customer’s browser should receive only the information needed to complete the payment journey.
When should I grant access to a paid feature?
Once your server verifies the payment outcome. Tie that result back to your application’s purchase reference before changing access.
YOUR PAYMENT TOOLKIT
The services behind this solution.
Build the right flow for applications.
Tell us how your business works and choose a payment route that fits.