digid pay

Theme

Settlement ​

Settlement is the movement of money from the card networks to you. In digid pay's model, funds flow directly from our European acquiring partner to your bank account — digid pay never holds or routes merchant funds.

Status. The direct-settlement model is architectural fact (AD-4). Settlement views in the dashboard are planned (FR-19).

How money moves ​

mermaid
sequenceDiagram
    participant Shopper
    participant Acquirer as Acquiring partner
    participant digidpay as digid pay
    participant Bank as Merchant's bank account
    Shopper->>Acquirer: card payment (via digid pay)
    Acquirer-->>digidpay: status + margin record (no funds)
    Acquirer->>Bank: settles directly (T+n)
    digidpay-->>digidpay: records settlement state + margin
  • You settle with the acquirer directly — digid pay is not in the money path.
  • digid pay's margin is captured via the acquirer's reseller mechanism per your plan. It never touches your settlement.
  • digid pay never holds or routes merchant funds. That is a boundary, not a detail — it is why digid pay is not a payments institution holding your money.

What you see ​

Each successful PaymentIntent shows a settlement state derived from the acquirer-side record:

StateMeaning
pendingAuthorised + captured; scheduled for the next payout cycle.
paidSettled to your account.

Periodic settlement summaries reconcile to the same transaction set, and all data is tenant-scoped — merchant A never sees merchant B's settlement.

Timing (T+n) ​

Payout timing is set by the acquirer (typically a few business days after capture). The exact schedule for your account is visible in the dashboard once settlement views ship. digid pay does not control or accelerate it.

Refunds vs settlement ​

  • A refund reverses a captured amount; it nets against a future payout.
  • A dispute is a separate chargeback flow (Disputes).
  • Track both separately from your own payout reconciliation.

digid pay — built in Europe.

© 2026 digid