Request a payout

POST /v1/partners/payouts

Moves your balance to a bank account.

Permission	request-payout — issued by Moria, not creatable in the console
Idempotency	Required — X-Idempotency-Key, 8–128 characters
Answers	200

Request

POST /v1/partners/payouts
Authorization: Bearer sk_live_xxxxxxxxxxxxxxxx
x-partner-signature: <hmac-sha256 of the raw body, hex>
X-Idempotency-Key: payout-2026-09-03-001
Content-Type: application/json

{
  "amount": "500000",
  "bank_code": "BRI",
  "bank_account_number": "888801000157508",
  "beneficiary_name": "Koperasi Al-Fath"
}

Field	Required	Notes
amount	yes	Decimal string
bank_code	yes
bank_account_number	yes
beneficiary_name	no	Recorded and shown on your statements

Response

{
  "data": {
    "id": "8a21…",
    "reference": "PGW-8A21C4…",
    "status": "pending",
    "is_final": false,
    "amount": "500000.0000",
    "fee": "5000.0000",
    "net_amount": "495000.0000",
    "currency": "IDR",
    "bank_code": "BRI",
    "bank_account_number": "888801000157508",
    "status_url": "/v1/partners/payouts/8a21…",
    "created_at": "2026-09-03T07:10:00.000Z",
    "finalized_at": null
  },
  "request_id": "req_…"
}

The amount is reserved before the transfer is sent, so the same money can never be promised twice. Under the default DEDUCTED mode, fee stays behind and net_amount is what reaches the bank. A failed payout returns the full reservation and your balance goes back up.

An unclear outcome keeps your money reserved

Never re-send under a new key

Moria returns a reservation only on positive evidence that the provider refused. Not on a timeout, not on a dropped connection, not on an answer that could mean either thing.

The asymmetry is deliberate: releasing a reservation for money that actually left would let it be spent twice, and a bank transfer has no reversal.

So an uncertain payout stays pending, amount still reserved, until Moria establishes the truth from the provider. Poll it, or retry with the same key. A new key is a second transfer.

Limits

Moria sets these per partner. Your operations team can see them, and what is left, on the Pencairan page of the console.

Limit	Meaning
Per transaction	The largest single payout
Per day	A rolling 24 hours, not a calendar day
Per hour	A count, not an amount

Two rules that look inconsistent and are not: a failed payout consumes none of the daily amount — the money came back — but it does count toward the hourly count. A burst of failures is what a stolen credential looks like.

Code	Means
FUNDS_INSUFFICIENT_BALANCE	available does not cover it
FUNDS_LIMIT_EXCEEDED	A limit would be breached
FUNDS_PAYOUT_SUSPENDED	Payouts are off for your account, or no limits are configured yet

No configuration means refused, not unlimited

A partner with no limits configured cannot pay out at all. Absent configuration means nobody has decided what you are allowed to do — which is not the same as being allowed everything.

Next

• Check your balance before requesting
• Payout detail to follow it to a terminal state