Transactions & Receipts

Overview

A transaction is the closed record of what happened in a session: who was identified, what they bought, which offers applied, how they paid, and what each money class moved. You can list and inspect transactions today; the void, receipt, dispute, settlement, and reconciliation operations are shape-frozen but not yet mounted.

Read The Decisioning Model first if you have not. A transaction is what the close call writes, and it carries the same two-class money split as every other surface.

Receipt-of-record: every identified transaction gets one

Every identified transaction produces a brand-wallet receipt, regardless of how it was paid. A wallet-paid order, a cash-paid order, and a card-paid order all generate the same receipt-of-record the moment the customer is resolved on the session. The tender does not gate the receipt; identity does.

This is the difference between a payments shim and a decisioning record. Feddi captures the transaction because the customer was identified, not because Feddi moved the money. A cash sale to a known customer is a first-class transaction with line items, applied offers, and attribution, even though no balance changed.

Operations

This domain mixes maturities. Two read operations are Beta and callable today; everything that mutates or reports is Planned.

List transactions (Beta)

GET /{integrationId}/transactions returns a cursor-paged feed of transaction summaries, scoped to your integration. Pass an x-api-key. Reads do not carry the request envelope.

curl "https://api.feddi.io/v1/partner/{integrationId}/transactions?status=completed&limit=50" \
  -H "x-api-key: $FEDDI_API_KEY"

{
  "ok": true,
  "data": [
    {
      "transaction_id": "tx_77c1",
      "receipt_number": "RCT-2026-000812",
      "transaction_type": "PAYMENT",
      "transaction_subtype": "BALANCE",
      "status": "completed",
      "amount_minor": 4500,
      "currency": "QAR",
      "applied_discount_minor": 500,
      "customer_phone": "+97433001122",
      "customer_name": "Layla A.",
      "identified_method": "qr",
      "branch_id": "22222222-2222-2222-2222-222222222222",
      "branch_name": "City Center",
      "partner_session_id": "ord-99812",
      "feddi_session_id": "33333333-3333-3333-3333-333333333333",
      "created_at": "2026-06-05T09:14:00Z"
    }
  ],
  "error": null,
  "meta": {
    "request_id": "req_tl1",
    "idempotency_replayed": false,
    "api_version": "2026-06-01",
    "next_cursor": "eyJjIjoxMDB9",
    "has_more": true,
    "data_completeness_score": 71
  }
}

Get one transaction (Beta)

GET /{integrationId}/transactions/{transactionId} returns the full detail for one record: the flattened customer, wallet, program, branch, brand, and enterprise; reconstructed line_items; the applied_offers that touched the charge; and related_transactions so you can render the full money lineage of an order (refunds, the original deposit, sibling rows that share a multi-transaction group).

Money is minor units plus an explicit currency. Metadata is sanitized server-side, so redemption secrets never leak into the response.

curl "https://api.feddi.io/v1/partner/{integrationId}/transactions/tx_77c1" \
  -H "x-api-key: $FEDDI_API_KEY"

{
  "ok": true,
  "data": {
    "transaction_id": "tx_77c1",
    "receipt_number": "RCT-2026-000812",
    "transaction_type": "PAYMENT",
    "transaction_subtype": "BALANCE",
    "status": "completed",
    "amount_minor": 4500,
    "currency": "QAR",
    "applied_discount_minor": 500,
    "customer": {
      "wallet_user_id": "wu_5512",
      "phone": "+97433001122",
      "name": "Layla A.",
      "identified_method": "qr",
      "customer_state": "verified"
    },
    "wallet_id": "wal_5512",
    "wallet_program_name": "VIP Rewards",
    "branch": { "id": "22222222-2222-2222-2222-222222222222", "name": "City Center", "status": "ACTIVE" },
    "partner_session_id": "ord-99812",
    "feddi_session_id": "33333333-3333-3333-3333-333333333333",
    "line_items": [
      { "sku": "LATTE-L", "name": "Large Latte", "quantity": 2, "unit_price_minor": 2000, "extended_price_minor": 4000, "discount_minor": 0, "tax_minor": 200, "category": "beverages" },
      { "sku": "CROISSANT", "name": "Butter Croissant", "quantity": 1, "unit_price_minor": 1000, "extended_price_minor": 1000, "discount_minor": 500, "tax_minor": 25, "category": "bakery" }
    ],
    "applied_offers": [
      { "offer_id": "off_22", "name": "Croissant 50% off", "discount_minor": 500, "source": "rule" }
    ],
    "related_transactions": [
      { "transaction_id": "tx_dep_44", "transaction_type": "DEPOSIT", "amount_minor": 10000, "status": "completed", "created_at": "2026-06-04T18:00:00Z" }
    ],
    "created_at": "2026-06-05T09:14:00Z",
    "updated_at": "2026-06-05T09:14:00Z"
  },
  "error": null,
  "meta": { "request_id": "req_td1", "idempotency_replayed": false, "api_version": "2026-06-01", "data_completeness_score": 92 }
}

Corrections: void vs unattach vs dispute (Planned)

Three distinct compensations exist for three distinct mistakes. They are shape-frozen and not yet callable. Do not conflate them.

Receipts: get, reprint, resend (Planned)

The receipt-of-record can be rendered and re-delivered without changing the transaction. These are shape-frozen.

• GET /{integrationId}/transactions/{transactionId}/receipt renders the receipt-of-record (html, pdf, or thermal).
• POST /{integrationId}/transactions/{transactionId}/receipt/reprint reprints a lost or jammed receipt, or a manager copy.
• POST /{integrationId}/transactions/{transactionId}/receipt/resend re-delivers a receipt to the customer's wallet or SMS.

Settlement and reconciliation (Planned)

These reporting surfaces close the books. They are ledger-and-report endpoints, never custody surfaces: Feddi never holds the money (see The Decisioning Model).

GET /{integrationId}/transactions/export bulk-exports transactions as CSV or XLSX (synchronous for small ranges, asynchronous for large ones).

Where to go next