Skip to content

AXK is live: verification and settlement for commodity trade across the Global South.Request a briefing

AXK Network

AXK documentation

How AXK models a commodity trade, from evidence to settlement, and how your systems connect to it. The full API reference and sandbox credentials are shared during onboarding.

Overview

AXK keeps one record per trade. Parties add evidence, the platform checks it against the contract, and payment obligations become payable only when their conditions are met. Licensed partners hold funds and execute payments; AXK orchestrates instructions, tracks finality and reconciles every beneficiary. See the protocol for the rules every trade follows.

Getting access

  1. Request a briefing and tell us your role, commodities and corridors.
  2. Complete KYB: company documents, beneficial owners and screening.
  3. Receive workspace access, sandbox API keys and webhook signing secrets.
  4. Agree your contract templates, document sets and payment routes, then go live.

Request a briefing to begin.

Core concepts

Trade
A commodity contract between parties: terms, specification, Incoterms, the document set and every event against it.
Lot
A physical quantity with its own origin, lineage and custody history. Lots split and merge; lineage is kept.
Document
A certificate, declaration or transport document with its issuer, issue time and a SHA-256 integrity hash.
Obligation
An approved amount owed by one party to one or more beneficiaries, with one stable reference across every rail.
Allocation
The split of an obligation into beneficiary amounts in integer minor units, summing exactly to the total.
Payment
One instruction on one rail to one beneficiary, tracked through the settlement state machine.
Posting
A balanced double-entry journal line. Postings are never edited; corrections are compensating entries.
Disclosure
A consented, scoped, expiring grant that lets another party see part of a trade record.

Evidence packs

An evidence pack is a scoped export of a trade record for one purpose: an EUDR due-diligence statement, a CBAM declaration, a lender's credit file or an auditor's request. Each pack lists its documents with issuer, time and hash, the custody chain for the lots it covers, and the screening results for each counterparty. Packs are shared by consent and every access is logged.

{
  "pack": "pk_01J9…",
  "purpose": "eudr_dds",
  "trade": "TRD-00418",
  "lots": ["LOT-KE-2291", "LOT-KE-2292"],
  "plots": { "type": "FeatureCollection", "features": 214 },
  "documents": [
    { "type": "inspection_certificate", "issuer": "Independent inspector", "sha256": "9f2c…e81a" },
    { "type": "certificate_of_origin", "issuer": "Chamber of commerce", "sha256": "41ab…07d3" }
  ],
  "disclosure": { "to": "buyer", "expires": "2027-01-31", "revocable": true }
}

Events

Every state change is an immutable, signed event. These are the events on the settlement path:

  • TradeVerifiedContract terms accepted, counterparties screened, origin, inspection and custody evidence checked against the contract.
  • ObligationApprovedA payment obligation with one stable reference is approved by a separate authority from the one that created it.
  • FundingConfirmedFunds are confirmed received by the licensed institution holding them, matched to the obligation.
  • SettlementSubmittedInstructions go to the selected rail with an idempotency key derived from the obligation.
  • ProviderFinalityConfirmedThe bank, mobile-money operator or settlement network confirms final, irreversible completion.
  • RecipientReconciledProvider statements are matched per beneficiary; balanced postings close the obligation.
  • ReceiptIssuedA receipt with the full event chain and document hashes is issued to every party entitled to see it.

Webhooks

AXK delivers events to your endpoint as signed JSON. Verify the AXK-Signature header (HMAC-SHA256 over the timestamp and raw body) before trusting a payload, reject timestamps older than five minutes, and treat delivery as at-least-once by de-duplicating on event.id.

POST /your/webhook
AXK-Signature: t=1760438400,v1=5c0e…b2a9

{
  "id": "evt_01J9…",
  "type": "ProviderFinalityConfirmed",
  "trade": "TRD-00418",
  "obligation": "OBL-00418-01",
  "payment": { "rail": "mobile_money", "beneficiary": "BEN-1187", "amount": 482300, "currency": "KES" },
  "occurred_at": "2026-10-14T09:12:44Z"
}

Idempotency & retries

Every write accepts an Idempotency-Key. For payments, AXK derives the key from the obligation and beneficiary, so the same payment can never be created twice. A provider timeout moves a payment to Uncertain; AXK queries the original provider and reconciles statements before any retry. Only a confirmed failure is retried, with the same key.

ISO 20022

Payment instructions and statuses with partner banks are aligned to ISO 20022:

  • pain.001Customer credit transfer initiation
  • pacs.008Financial institution credit transfer
  • pacs.002Payment status report
  • camt.053Bank-to-customer statement, used for reconciliation
  • camt.054Debit and credit notification

Glossary

DDS
Due-diligence statement filed by an operator under EUDR.
KYB
Know your business: identity, ownership and screening checks on a company.
UBO
Ultimate beneficial owner of a counterparty.
Incoterms
ICC rules defining who carries cost and risk at each stage of delivery, such as FOB or CIF.
Bill of lading
Carrier's receipt and title document for goods shipped by sea.
Warehouse receipt
Document of title for stock held in a certified warehouse, often used as collateral.
Finality
The point at which a payment can no longer be reversed by the provider.
Minor units
The smallest unit of a currency, such as cents. All AXK amounts are integers in minor units.

Payloads on this page are examples. Field names and endpoints are confirmed in the API reference shared during onboarding.