Skip to content

Chargebacks after release ​

Sometimes a bank or payment provider takes a buyer's payment back after RekberPay already released the money to the seller. This is a chargeback (a payment reversal). It is rare, but it can happen weeks after the order was done, so plan for it.

Who is responsible ​

Under your Platform agreement, you, the partner, are responsible to RekberPay for chargebacks on your marketplace, for the full amount the gateway reversed. That includes RekberPay's fees and the payment method fee, not only what the seller received. RekberPay first takes the money back from partner balances (see below). Whatever that does not cover is a receivable: an amount your workspace owes RekberPay.

How the reversal works ​

RekberPay's team reverses the release once the gateway confirms the chargeback. You do not call anything.

  1. The amount owed is everything the gateway took back: the order amount, the buyer fee and the payment method fee.
  2. RekberPay takes it from partner balances, each as far as it goes. A balance never goes below zero.
    • After a release, from the seller's partner balance. The seller is debited the full amount the gateway reversed, including RekberPay's fee and the payment method fee, even though the seller received less. For example: the buyer paid Rp54.500, the seller received Rp45.000, the gateway reverses Rp54.500, so up to Rp54.500 comes from the seller's partner balance.
    • After a split, the buyer got part of the money back on their partner balance and the whole payment back from their bank. That split credit comes back from the buyer's partner balance first (at most the credit). The rest of the amount comes from the seller's partner balance (at most the amount less the buyer's credit). The seller never pays for money the buyer kept.
    • After a refund to the buyer's partner balance (a dispute refund or the automatic refund when the seller did not ship), the buyer holds the refund twice, so it comes back from the buyer's partner balance (at most the refund). The seller got nothing and is not touched.
  3. Whatever is left becomes a receivable owed by your workspace.
  4. The buyer is not paid again on RekberPay. Their bank already gave the money back, so a second credit would pay them twice.
  5. RekberPay keeps the fees it charged on that order; they are part of what you owe.
  6. The milestone keeps its status (released or refunded). The settlement did happen; the chargeback is a later money event on the same milestone, so your order status does not move backwards.

A milestone paid from the buyer's partner balance cannot be charged back (no gateway took that payment), and each milestone can be reversed only once. A Sandbox milestone is never charged back, because no gateway took a real payment, so there is nothing to simulate: build your handler from the payload below.

The webhook ​

You get milestone.release_reversed the moment the reversal is recorded:

json
{
  "event": "milestone.release_reversed",
  "data": {
    "next": {
      "status": "released",
      "partner_order_ref": "ORD-1042",
      "buyer_ref": "u_881",
      "seller_ref": "u_310",
      "settlement": "release",
      "amount": 103500,
      "recovered_amount": 40000,
      "buyer_recovered_amount": 0,
      "seller_recovered_amount": 40000,
      "receivable_amount": 63500,
      "deal_status": "completed"
    }
  }
}
FieldMeaning
settlementWhat was reversed: release, split or refund. status is released for the first two, refunded for the last.
amountThe full amount the gateway reversed: the order amount, the buyer fee and the payment method fee.
recovered_amountThe part taken from partner balances: buyer_recovered_amount + seller_recovered_amount.
buyer_recovered_amountTaken back from the buyer's partner balance (a split or refund credit). 0 after a release.
seller_recovered_amountTaken from the seller's partner balance. 0 after a refund.
receivable_amountThe part your workspace owes RekberPay. 0 when the balances covered it all.

amount is always recovered_amount + receivable_amount. Like every Platform event, it names people by partner_user_ref only, never by user id.

A good handler lowers the buyer's and the seller's balances in your own records by buyer_recovered_amount and seller_recovered_amount, and, if receivable_amount is above zero, decides how you recover that amount from the seller on your side.

The receivable ​

Each receivable shows on the Payouts page of your RekberPay dashboard, under Chargeback receivables, in the mode you are viewing. It is read only. It is due 14 days after the chargeback is recorded, and the dashboard shows the due date next to it. RekberPay's team contacts you to settle it outside the system and marks it paid once it arrives. It is not deducted from your users' balances automatically. There is no late fee. If a receivable is still open after its due date, RekberPay may take it from your deposit (see below), and may pause new Live orders until it is paid.

Chargeback deposit ​

If chargebacks in one month get too high, RekberPay asks for a deposit. It is a cushion for chargebacks you have not paid yet, and most of it comes back to you. This is the standard rule for every Platform partner. Your signed agreement can set other numbers, and the dashboard always shows the ones that apply to you.

When it is asked. In a calendar month (Indonesian time, WIB), your chargebacks are more than 1% of that month's volume. Volume is what buyers paid through a payment method that month, less orders cancelled, refunded or charged back. Orders paid from a partner balance are left out, because they cannot be charged back. A chargeback counts in the month it was reversed. A closed month is never reopened. Sandbox never counts toward Live.

How much. 5% of that month's volume, asked only when that comes to at least Rp100.000. When 5% is under Rp100.000, no deposit is asked for that month. Your agreement can set a start month for the deposit, for example 3 months after you go Live. Chargeback recovery and receivables apply from your first Live day.

How to pay. You are told within the first days of the next month, by deposit.required, an email and a notice in the dashboard to your owner and finance members. Pay it within 7 days from the Deposit tab on the Payouts page, with a Virtual Account, QRIS or another method on the list. Each method shows its own payment fee before you pay, and you pay that fee on top of the deposit. A bank transfer or a static QRIS cannot be used. The deposit is paid in the dashboard only, not through the API, and a member with the finance role pays it.

What it can be used for. Only a chargeback receivable that is past its due date. RekberPay takes it the next day, oldest first, and tells you in the same moment: deposit.applied, an email and a line in the Deposit tab, with the order, the amount taken, what is left, and the top up now owed. If the deposit is lower than what is required after that, you get a top up due in 7 days. The deposit is used for nothing else.

When it comes back. The deposit is held until the end of the month after the month that went over. On the 1st of the next month RekberPay checks again. If that month was at 1% or lower and no receivable is open, the return of the rest of the deposit starts on the 1st and usually arrives within 2 working days in your verified payout bank account, minus the transfer fee, the same fee as a withdrawal. RekberPay's team makes the transfer, and you get deposit.returned once it is recorded. Example: more than 1% in March, held to 30 April, the return starts on 1 May. If you have no verified payout account, the return waits until you add one.

If the ratio stays high. The deposit stays and is set to 5% of the latest month's volume. A higher amount asks a top up, a lower one returns the difference on the 1st (an excess under Rp100.000 stays until the full return). It is checked again at the end of the next month.

The events, in the order they usually come:

EventWhen
deposit.requiredA deposit, or a top up, is due. Sent again with status: overdue when the due date passes
deposit.paidA payment arrived. status: held once the required amount is paid
deposit.appliedPart of it was used for a past due receivable
deposit.returnedThe excess, or the whole deposit, was sent to your bank account
json
{
  "event": "deposit.applied",
  "data": {
    "next": {
      "deposit_id": "0d9f6a52-7b0e-4f7c-8d6a-2f1e7c4d9a31",
      "receivable_id": "7c2a1e64-3b9d-4d58-a0f1-5e8b6c9d2a10",
      "partner_order_ref": "ORD-1042",
      "amount": 63500,
      "available": 436500,
      "topup_amount": 63500,
      "topup_due_at": "2026-12-09T09:00:00.000Z"
    }
  }
}

Each payload is listed in the Platform reference. They name no person, only your deposit and your own order ids. Answer 2xx to any event you do not handle.

Pausing new Live orders ​

If a deposit or a receivable stays unpaid after its due date, RekberPay may pause new Live orders for your workspace. Nobody is paused automatically: for a deposit you get reminders 3 days and 1 day before the due date and then the overdue notice, for a receivable a reminder 1 day before, and the team decides. This is separate from a full freeze and never touches Sandbox.

While it is on:

  • POST /v1/enterprise/platform/deals answers 423 NEW_ORDERS_PAUSED.
  • A buyer cannot start the first payment on an order that has nothing paid yet. The buyer page says so, with the same code. Creating a checkout link still works, but the buyer's first payment is refused with 423 NEW_ORDERS_PAUSED while the pause is on.

Everything else keeps working, so sellers and buyers in the middle of a deal are not hurt: the next payment on an order already paid in part, payments that were already started, shipping, confirming, releases to sellers, disputes, refunds, withdrawals, reads, KYC, ratings and chat. You can also pay the deposit or settle a receivable while it is on. The Payouts page shows a banner while it lasts, and RekberPay lifts it once what is owed is paid.

Treat 423 NEW_ORDERS_PAUSED as a temporary stop: keep the order in your own system and try again later, or contact RekberPay.

See also ​

Escrow, payment services and B2B deals for Indonesian businesses.