Add a payment checkout to your website or app. You create a session with the order details, display the Dintero-hosted checkout (embedded or as a redirect), and receive a callback when the customer has paid. This is the standard integration for any online store or service that needs to collect a one-time payment.Documentation Index
Fetch the complete documentation index at: https://docs.dintero.com/llms.txt
Use this file to discover all available pages before exploring further.
Integration steps
Create API credentials
In Backoffice, go to Settings > API clients and create a new Checkout client. Save the Client ID and Client Secret. The secret is only shown once.Use your sandbox account (
T prefix) while developing. Switch to production (P prefix) when you’re ready to accept real payments.Authenticate
Exchange your credentials for a bearer token using the OAuth 2.0 client credentials flow. The token is valid for 4 hours and is used in the
Authorization header for all API calls.See Authentication for details.Create a checkout session
Send a
POST request to /v1/sessions-profile with the order details: items, amounts, currency, and URLs for the callback and customer redirect.The response returns a session ID and a checkout URL that you use to display the payment page.See Create a session for the full payload reference.Display the checkout
Show the checkout to the customer. You have two options:
- Redirect: send the customer to the Dintero-hosted checkout page. Minimal setup, no iframe.
- Embed: render the checkout inside your page using the Web SDK. More control over the experience.
Handle the payment result
After the customer pays, Dintero notifies you through two channels:
Always verify the transaction via the callback. The browser redirect can fail if the customer closes the tab.See Handling payment for transaction statuses and handling.
| Channel | How | Use for |
|---|---|---|
| callback_url | Server-to-server GET request (retried up to 20 times) | Verify payment and fulfill the order |
| return_url | Customer browser redirect (not guaranteed) | Show a confirmation page |
Manage transactions
After authorization, you can capture, void, or refund transactions through the Transactions API. Most integrations capture when the order is shipped.See Transaction management for available operations and the state diagram for how transactions move between statuses.
What’s next
Quickstart
End-to-end walkthrough with code examples in cURL, Python, and Node.js.
Test data
Test cards and sandbox scenarios for verifying your integration.
Payment profiles
Configure which payment methods are shown in the checkout.
Webhooks
Subscribe to real-time transaction events.