The Check‑In Ledger:
rebuilding trust inside RedDoorz Affiliate

Where the commission comes from

RedDoorz Affiliate — internally called Redseller — is one leg of RedDoorz's B2B2C distribution: instead of selling rooms only through OTAs or its own app, RedDoorz opens a channel where individual resellers generate their own promo code, share it on social media, and earn a commission on every confirmed booking that comes through it.

Because affiliate discount codes were becoming a viral discovery pattern — resellers posting codes on Instagram, TikTok, WhatsApp groups — every reseller code was standardized with an RDAFF prefix. That single naming rule let pricing and ops instantly tell an affiliate-originated code apart from a market-wide promo, so affiliate discounts could be capped, governed, and reported on without leaking into the general promotions the marketing team runs.

Exhibit A

Code creation. Discount, validity window (max 365 days) and the RDAFF prefix are set once, upfront.

Exhibit B

Go-live. The reseller is prompted straight to social — the code only earns once it's shared.

Exhibit C

Home base. Commission-to-date and active code count sit above the fold, before any promotional content.

One reseller, up to five live codes

Resellers can run several codes in parallel — a cap of five active at a time — each with its own window and its own status. Every card carries the same ticket-stub shape as a physical coupon: a small, deliberate echo of what a promo code actually is.

Exhibit D

Live code. RDAFFFARAHQOONITAZZS, 3.0% discount, running 13 Aug – 09 Sep 2026.

Exhibit E

History. Expired codes stay visible with their own order and commission counts — nothing is deleted.

What the old logic paid for

The original rule paid 10% commission the moment a booking reached PAH — Pay at Hotel — status. That's an intent signal, not a fact: the guest hadn't checked in, hadn't paid, hadn't necessarily existed as a real stay at all.

At the scale of 8 million registered resellers, that gap didn't stay theoretical. A subset of resellers learned they could generate PAH bookings that would never convert into an actual check-in, collect the commission trigger anyway, and repeat it. No single case looked dramatic — but multiplied across the base, the leak became a recurring, structural loss.

Moving the trigger from intent to fact

The redesign moves commission eligibility from a booking event to a verified stay event: commission is only released once the guest has actually checked in at the property. It's a one-line change in principle — pay for a stay, not for a booking — but it closes the exploit without touching legitimate resellers' earnings.

Paired with the logic change, reseller onboarding now runs eKYC through Xendit, verifying each reseller's KTP (Indonesian national ID) at signup. Gating commission on a real check-in closes the exploit; gating accounts on a verified identity makes it far harder to route the same pattern through duplicate or fake reseller profiles.

The payout side was rebuilt to make each state legible instead of a single opaque number:

Exhibit F

Pending. Booked, not yet earned — sits at Rp 0 until the check-in gate clears.

Exhibit G

Cleared. Booking cutoff and payout window shown together, plus historical batches.

Exhibit H

Cancelled. Even a reversed payout is itemized — room commission, add-ons, 2.5% tax — so nothing is a black box.

Giving resellers something to actually read

A trust fix that no one can see doesn't build trust. Alongside the backend change, the dashboard was rebuilt so resellers can watch their own performance instead of waiting on a lump sum.

Exhibit I

Room-night trend. Total vs. confirmed nights, switchable by week, month, or custom range.

Exhibit J

Command center. Orders, commission, price requests, and promo codes — one entry point, not four separate flows.

Exhibit K

Price requests. Resellers can propose a selling price against the property's floor before a booking completes.

The product operations layer underneath all of it

None of the above ships as a single engineering ticket — it's a product operations problem: the same reseller base, the same booking data, and the same commission ledger were running through four disconnected flows, each with its own edge cases, its own manual checks, and its own way of quietly hiding fraud. The work was as much about removing steps as adding them.

Every one of these was a standing operational cost before it was a fraud problem: ops manually reconciling PAH bookings against actual stays, support fielding "where's my commission" tickets because the payout logic wasn't visible anywhere, and no single naming convention to separate an affiliate discount from a market promo. Simplifying the reseller-facing product and closing the fraud gap turned out to be the same exercise — fewer manual touchpoints meant fewer places for the exploit to hide, and a clearer surface for the reseller to trust.