Kravia invoice delivery

By default, invoices are delivered to your customers automatically. You can instead choose to deliver invoices yourself by setting invoice_channel: "merchant". This gives you control over the delivery method, timing, and branding. It works with both customer checkout and merchant initiated.

You need to request access to the invoice delivery feature from support.

How it works

Before delivering the invoice to the customer, you must call POST /v1/transactions/{id}/capture to start collection. The transaction status remains AUTHORIZED; an INITIATE_CAPTURE event is added to mark that collection has begun. Without this, Kravia will not start collection. If configuration.auto_capture is true, collection starts immediately, so distribution of the invoice should be done promptly.

Configuration

Set invoice_channel: "merchant" to enable custom distribution.

Session-level configuration (Customer checkout)

POST /v1/sessions-profile
Authorization: Bearer <token>
Content-Type: application/json

{
  "url": {
    "return_url": "https://example.com/accept",
    "callback_url": "https://example.com/callback"
  },
  "order": {
    "amount": 50000,
    "currency": "NOK",
    "merchant_reference": "order-123",
    "items": [ ... ]
  },
  "configuration": {
    "kravia": {
      "type": "payment_type",
      "invoice_b2b": {
        "type": "payment_product_type",
        "enabled": true,
        "days_until_due": 14,
        "invoice_channel": "merchant"
      }
    }
  }
}

Payment-level configuration (merchant initiated)

POST /v1/sessions/pay
Authorization: Bearer <token>
Content-Type: application/json

{
  "payment": {
    "payment_product_type": "kravia.invoice_b2b",
    "operation": "invoice_payment",
    "days_until_due": 14,
    "invoice_channel": "merchant"
  },
  "session": {
    "url": {
      "callback_url": "https://example.com/callback"
    },
    "order": {
      "amount": 50000,
      "currency": "NOK",
      "merchant_reference": "inv-2026-001",
      "billing_address": { ... }
    }
  }
}

Configuration precedence

The value is resolved in this order:

Session/payment configuration (highest priority)
Checkout payment options (fallback)
Default: "kravia"

Delivering the invoice

After the transaction is AUTHORIZED, the Kravia invoice has been created and is ready for delivery. Before you deliver it through your own channel, capture the transaction to start collection with Kravia.

1. Capture the transaction

Call capture to start collection with Kravia:

POST /v1/transactions/T12345/capture
Authorization: Bearer <token>
Content-Type: application/json

{
  "amount": 50000,
  "items": [
    {
      "line_id": "1",
      "amount": 50000
    }
  ]
}

The transaction status stays AUTHORIZED; an INITIATE_CAPTURE event is appended to record that collection has started. The transaction will move to CAPTURED (or PARTIALLY_CAPTURED) once Kravia confirms the shopper has paid. For shared capture semantics, see Transaction management.

2. Deliver through your channel

Send the invoice to your customer through your own channel, such as email, SMS, a third-party platform, your ERP system, or any other channel. To send the generated invoice, use the kravia:invoice_url value from the transaction metadata to retrieve the generated PDF:

{
  "metadata": {
    "kravia:invoice_number": "16788-000018",
    "kravia:invoice_url": "https://checkout.dintero.com/transaction-attachments/..."
  }
}

To generate your own invoice document, use the payment details returned in the INITIATE_CAPTURE event metadata:

{
  "events": [
    {
      "event": "INITIATE_CAPTURE",
      "metadata": {
        "kravia:invoice_number": "16788-000018",
        "kravia:invoice_id": "98765",
        "kravia:payment_details:bank_account:bban": "15063092174",
        "kravia:payment_details:bank_account:iban": "NO0215063092174",
        "kravia:payment_details:bank_account:swift": "DNBANOKKXXX",
        "kravia:payment_details:kid": "300000019497814"
      }
    }
  ]
}

These payment details allow the customer’s payment to be matched by Kravia.

Generated invoice documents must match the session data. Kravia uses the session as the source of truth for collection.

Cancellations

Refund is not supported for Kravia. To cancel an invoice (including one delivered through your own channel), use POST /v1/transactions/{id}/void. See Cancellations in Customer checkout for the full rules per state.

Checkout Integration

Express Checkout

In-Person Payments

Payment Methods

Tokenization

Split Payout

How it works

Configuration

Session-level configuration (Customer checkout)

Payment-level configuration (merchant initiated)

Configuration precedence

Delivering the invoice

1. Capture the transaction

2. Deliver through your channel

Cancellations

See also

​How it works

​Configuration

​Session-level configuration (Customer checkout)

​Payment-level configuration (merchant initiated)

​Configuration precedence

​Delivering the invoice

​1. Capture the transaction

​2. Deliver through your channel

​Cancellations

​See also

How it works

Configuration

Session-level configuration (Customer checkout)

Payment-level configuration (merchant initiated)

Configuration precedence

Delivering the invoice

1. Capture the transaction

2. Deliver through your channel

Cancellations

See also