It can be used by merchants who want to use the Dintero Checkout to collect customer details while handling the rest of the payment process themselves.
(Kravia begins delivery) Kravia->>Customer: Delivers invoice Customer->>Kravia: Pays invoice Kravia-->>Dintero: Payment confirmed Dintero-->>Merchant: Transaction CAPTURED Note over Dintero: settlement_status updates to SETTLED
when funds reach merchant ``` ## Step-by-Step Implementation ### 1. Configure Payment Types Enable the payment types you need in your payment profile or session configuration: ```json theme={null} { "configuration": { "kravia": { "type": "payment_type", "invoice_b2b": { "type": "payment_product_type", "enabled": true, "days_until_due": 14 }, "invoice_b2b_grouped": { "type": "payment_product_type", "enabled": true, "days_until_due": 14, "invoice_schedule": { "interval": "monthly" } }, "invoice_b2c": { "type": "payment_product_type", "enabled": true, "days_until_due": 14 } } } } ``` ### 2. Create Checkout Session ```http theme={null} POST /v1/sessions-profile Authorization: Bearer
INITIATE_CAPTURE event added
Payment details added alt Send generated invoice Merchant->>Customer: Send PDF URL else Generate own invoice Merchant->>Merchant: Generate invoice document Merchant->>Customer: Send invoice with payment details end Customer->>Kravia: Pays invoice Kravia-->>Dintero: Payment confirmed Dintero-->>Merchant: Transaction CAPTURED Note over Dintero: settlement_status updates to SETTLED
when funds reach merchant ```
Billing Address Requirements
Both flows require a billing address with the same fields as [customer checkout](/docs/checkout/kravia/checkout#billing-address-requirements). The location differs: in one-step it's in `session.order.billing_address`, in two-step it's in the pay request body. ## One-Step: Create and Pay A single call creates the session and registers the invoice: ```mermaid theme={null} sequenceDiagram participant Merchant participant Dintero Merchant->>Dintero: POST /v1/sessions/pay Dintero-->>Merchant: Transaction AUTHORIZED Note over Dintero: INITIATE_CAPTURE event added(Kravia begins delivery) ``` Identity verification is automatically skipped. The billing address is provided in `session.order.billing_address` (see [required fields](#billing-address)). The transaction is `AUTHORIZED` on creation and moves to `CAPTURED` once Kravia confirms the shopper has paid. ### B2B Example ```http theme={null} POST /v1/sessions/pay Authorization: Bearer
(Kravia begins delivery) ``` ### Step 1: Create the Session For B2B ```http theme={null} POST /v1/sessions Authorization: Bearer
Creating subscription for a new customer
1. Create a payment session with the subscription amount, [and specifies that a recurrence token should be created](/docs/checkout/tokenization-create-token#create-token-session) . 2. The customer [pays](/docs/checkout/display-checkout) 3. The merchant is [notified about the successful payment](/docs/checkout/after-payment#getting-notified-about-the-transaction-status). 4. The merchant [fetches and stores the token](/docs/checkout/tokenization-fetching-storing) ## Receive payment for subsequent periods 1. Create a [recurrence transaction](/docs/checkout/tokenization-use-token#recurrence-transactions) with the previously acquired token 2. The merchant will receive a synchronous response about the payment status, but should also implement a callback in case the request failed, but the payment succeeded in the background. ## Upgrading the subscription Let's say the customer has been a **tier 2** member for 6 months, but now they want to upgrade to **tier 3**. They paid 300 for the full year, and the price for **tier 3** is 500. 1. Repeat the steps from [Creating subscription for a new customer](#create-subscription) for the customer to pay 500. 2. [Refund the money] for the remaining 6 months of the **tier 2** membership, 150,- 3. The merchant stops using the old recurrence token and starts using the new for subsequent payments. [Refund the money]: /api-reference/transactions/transactions_id_refund_post # Auto-approve sellers Source: https://docs.dintero.com/docs/checkout/testdata/approvals/auto-approve Use magic values in the payout_destination_description field to auto-approve, decline, or wait for signature on a new split-payment seller in test. For testing purposes it is possible to auto-approve or decline a new seller by adding one of the following values to `payout_destination_description`: *- Dispute: return
- Dispute: goods not received
- Dispute: order already paid
- Dispute: faulty goods
- Dispute: incorrect invoice
- Dispute: high-risk order
- Dispute: unauthorized purchase
Void/cancel
If, for some reason, the order will not be fulfilled, you can cancel the transaction to release the money from the customer's account. A transaction can only be voided if it has not been captured. After the void is successful, the transaction status is changed to `AUTHORIZATION_VOIDED` #### Request **`POST`** `/v1/transactions/{id}/void` [Void] #### Response ```json theme={null} { "id": "...", ... "status": "AUTHORIZATION_VOIDED" } ``` ## Refund If the order, or parts of it, are returned, the money can be refunded. The refund amount cannot be larger than the captured amount.Dintero documentation
Dintero is a unified commerce platform that brings payments, loyalty, order management, and partner tools together. Whether you're building an online store, a marketplace, or a point-of-sale system, Dintero handles the financial infrastructure so you can focus on your product.Get started with payments
Other products
Loyalty & Virtual Cards
Manage customer profiles, run discount and loyalty programs, store digital receipts, and issue gift cards.
Order ManagementCreate and track orders independently of payment. Manage the full lifecycle from draft through authorization, capture, and refund.
PartnersAutomate merchant onboarding, configure payment settings, and pull reports on behalf of your merchants through the Partner API.