Core ledger APIs
Expense Management calls a small API on your core ledger: to look up funding accounts, to pay a merchant from a QR code, and to pay out reimbursements and supplier invoices. You host it at one base URL per environment and share that URL with us during onboarding.
See Core ledger APIs in our API reference for the full schemas.
If your core ledger already offers account lookup and payment APIs, talk to your Open Fabric contact. We can map Expense Management's calls to your existing API.
What you build
| Operation | Endpoint | Required |
|---|---|---|
| Get account | GET /v1/accounts/{account_ref} | Yes |
| List account events | GET /v1/accounts/{account_ref}/events | Optional |
| Submit QR payment | POST /v1/qr_payments | If you offer QR payments |
| Get QR payment | GET /v1/qr_payments/{payment_ref} | If you offer QR payments |
| Create payout | POST /v1/payouts | If you offer reimbursements or bill pay |
| Get payout | GET /v1/payouts/{payout_ref} | If you offer reimbursements or bill pay |
Principles
- No callbacks. Results come back to Expense Management as account events that carry Expense Management's reference in
transaction.expense_mgmt_ref. The get operations are a fallback for polling. - Idempotent on Expense Management's reference. A retry sends the same body with the same
payment_reforreference. Pay at most once per reference. If the same reference arrives with a different amount or beneficiary, answer409. - Never answer
404for a payment you know. A404on a get tells Expense Management you never received the payment, so it submits it again. - No holds, no FX and no cancel. Expense Management doesn't ask you to hold funds. Once a payment is submitted, it is yours to finish.
- Authentication is whatever you offer: OAuth 2.0 client credentials, an API key or mutual TLS. Issue a credential that is only valid for your own accounts and payments.
- Errors use the body
{"error_code": "...", "message": "..."}. Expense Management never shows yourmessageto users.
Get account
GET /v1/accounts/{account_ref}
Called when your staff link a funding account to a business, and to show the live balance on dashboards and before QR payments and payment runs.
{
"account_ref": "acc_7f3e",
"holder_name": "Acme Trading Pte. Ltd.",
"account_mask": "••••1234",
"currency": "SGD",
"available": { "amount": "49720.00", "currency": "SGD" },
"current": { "amount": "50000.00", "currency": "SGD" },
"as_of": "2026-11-04T09:15:00Z",
"last_sequence": 980
}
availableis what can be spent after your holds.currentis the posted balance.last_sequenceis thesequenceof the account's latest event, or0if it has none. Expense Management uses it as the starting point for gap detection.- Answer
404withaccount_not_foundfor an unknown account.
Account event list (optional)
GET /v1/accounts/{account_ref}/events?after_sequence=980&limit=100
Returns the account's events after a sequence, oldest first, in the same shape you post to account events. The response is {"data": [...], "has_more": false}. The default limit is 100 and the maximum is 500.
Expense Management calls it when it detects a gap in sequence. If you don't offer it, answer 404 and Expense Management waits for redelivery.
QR payments
POST /v1/qr_payments and GET /v1/qr_payments/{payment_ref}
When an employee scans a merchant's QR code in the app, Expense Management checks the payment against the policy and then asks you to pay.
{
"payment_ref": "qrp_01jbty0z0tfcz9mg0x5gxmmqv5",
"debtor": { "account_ref": "0123456789" },
"creditor": {
"name": "Marina Bay Hotel",
"city": "Singapore",
"country": "SG",
"mcc": "7011",
"merchant_account": "SG.PAYNOW:201234567R",
"acquirer_id": null
},
"amount": { "amount": "60.00", "currency": "SGD" },
"qr": { "standard": "sgqr", "payload": "000201010212..." }
}
- Run your own checks, debit the account and pay the merchant. You can call the authorization check with
qr.expense_mgmt_refset. It returns the decision already taken, without counting the payment twice. - Answer
201with the payment and itsstatus:completed(paid),rejected(not paid, with arejection_code) oraccepted(in progress). - For
accepted, post the final result later as an account event withtransaction.kind: qrandtransaction.expense_mgmt_refset to thepayment_ref. - A repeat of a known
payment_refanswers200with the payment as it stands.
Payouts
POST /v1/payouts and GET /v1/payouts/{payout_ref}
When a business's finance team approves a reimbursement run or a supplier payment, Expense Management asks you to pay from the funding account. Calls carry an Idempotency-Key header.
{
"reference": "pay_01jbzr7kq0f8rt5mx2vw3c4d5e",
"account_ref": "acc_7f3e",
"beneficiary": {
"account_name": "Rachel Tan",
"account_number": "0001234506789",
"bank_code": "BNKASGSG"
},
"amount": { "amount": "35.00", "currency": "SGD" }
}
- Answer
202with the payout and itsstatus:pending,sent,settled,returnedorfailed. - Post status changes as account events with
transaction.kind: payoutandtransaction.expense_mgmt_refset to thereference. - Answer
422withinsufficient_fundsorinvalid_beneficiaryif you can't pay. Nothing is paid. - Never return the beneficiary's full account number. Use
beneficiary_account_masked.
Failure handling
| Situation | What Expense Management does |
|---|---|
Timeout or 5xx on a submit | Retries with the same body and reference, then polls the get operation |
404 on a get | Treats the payment as never received and submits again |
401 | Gets a new token and retries once |
| Your API is down | Payment runs and QR payments wait and retry. Balances show as unavailable |