Lemak takes a payment in the payer's own currency through a local channel, converts it to US dollars at an aggregated rate plus a stated spread, and settles to you over USDC or SWIFT.
Payment
pi_AGQHAVEX7J327MRWOPILG46G6Y
1,000.00 THB
Four steps, from the payer's channel to your account. Each one is a state in the database, and each state change writes its ledger entry in the same transaction.
A payer pays through a local channel: a bank QR, a wallet, a redirect. The channel calls back. Before anything is marked paid, we call the channel's own query, and the amount, currency and status must agree.
Quotes from several sources are trimmed of outliers and averaged into an immutable snapshot. Your rate is that mid plus a spread in basis points, fixed at the point you choose: order, payment or channel settlement.
Money is pending until the channel's statement confirms that it arrived. It is available three days after that by default.
USD to you over USDC or SWIFT. Both rails are operated by hand today: a person sends each payout from a queue, and two people sign the receipt.
The table you work from and the journal we post are two readings of one record. There is no second store to disagree with the first.
| Amount | Method | Payment | Status | Net |
|---|---|---|---|---|
| 1,000.00 THB | PromptPay | pi_AGQH…G6Y | Paid | 27.63 USD |
| 2,450.00 PHP | QR Ph | pi_7KWQ…2XB | Paid | 41.88 USD |
| 560.00 THB | PromptPay | pi_M4TB…J9L | Requires payment | — |
| 18,900.00 PHP | QR Ph | pi_QZ2E…R4V | Failed | — |
| Account | Debit | Credit |
|---|---|---|
| Channel receivable | 1,000.00 | — |
| Merchant pending | — | 975.00 |
| Fee revenue | — | 25.00 |
| Journal | 1,000.00 | 1,000.00 |
Balanced per currency at commit, written in the same transaction as the state it records, and append-only after.
Each one is described in full in the specification, beside the code that does it.
A REST API. A repeated idempotency key replays the original answer, so a retry never charges the payer twice.
In the specificationThe page shows the payer who is being paid and the methods that routing can serve. It holds no key.
In the specificationQuotes are aggregated, outliers are rejected, the spread is stated, the snapshot is immutable, and the rate locks at the point you choose.
In the specificationMoney is pending until the statement matches and is released on T+3. A change of payout account holds the next settlement for 24 hours and needs a second approver.
In the specificationDouble-entry and append-only. Every journal is balanced per currency at commit.
In the specificationOne statement per account, day and currency. Only a matched line moves money. Everything else waits for a person.
In the specificationEach control is held by the database or by a test, not by this page.
Four measures keep the ledger append-only: an insert-only grant, a revoke from every other role, a row trigger that stops the owner, and a statement trigger that stops a truncate.
One atomic insert claims an idempotency key. Two retries of one request cannot both proceed.
A key is 130 bits from crypto/rand, shown once and stored as a digest. Requests are signed by HMAC or by Ed25519, and with Ed25519 we never hold the private half.
Every secret we issue is derived from one master key by purpose. None of them is stored.
A fee, a spread, an adjustment and a payout account change each need a second approver. The database refuses the change when the maker is also the checker.
Every administrative write commits its audit row in the same transaction as the change.
Three parts, each a row you can read: a fee on the payment, a spread on the rate, and a fee on a dispute. Here is the example this site uses.
Paid in
1,000.00 THB
The payer's amount, in minor units from end to end.
After the fee
975.00 THB
A payment fee of 2.5%, from the fee row in force when the payment was made.
Rate
35.28
An aggregated mid of 35.00 plus a spread of 80 basis points, kept to twelve places.
Settled
27.63 USD
Rounded down. The remainder is booked to a named account, not kept loose.
The PRODUCT specification's worked example. Your rates are the ones in your agreement. How a price is built, in full
Lemak is Malay and Indonesian for rich, or creamy, as in nasi lemak: rice cooked in coconut milk. Our markets are in Southeast Asia, so the coconut palm is the one picture that carries the name.
The Straits trade settled through the bill of exchange. Money was paid in at one house and paid out at another, in another currency. The two houses settled between themselves on one book.
That is this business, with better clocks. The motto on the crest, per unum librum, means "through one book".
What is true today, without spin.
| Markets | The Philippines, by QR Ph, through one production adapter, measured against the live provider. Its callback wire format is unverified until a public endpoint and a paid order exist. Thailand (PromptPay), Indonesia and Vietnam are planned. Test mode runs every method through a mock channel. |
|---|---|
| Settlement | USD only. USDC and SWIFT, both manual. |
| Onboarding | Our operators create each account. There is no self-service sign-up. |
| Status | Not live. No environment holds merchant funds. Every statement on this site describes what the code does, verified by its tests against a live database. |
| Integration | The specification is public, and you can read it before any contact. |
Each endpoint has its own secret. The signature covers the timestamp and the body as one string.
A new payout account needs a second approver, and the next settlement waits 24 hours after it.
The Philippines adapter, built against the live provider and measured there.
The hosted page shows the payer who is being paid.
To talk to us, book a demo. The form goes to a person on our sales team, who replies by email. The specification says what is built, what is not, and how each part is verified, so you can read it first.