Ratings

A rating on a marketplace deal is the same rating people give each other on a direct rekber. It counts toward one reputation on RekberPay, shown on the person's public profile at rekberpay.com/u/<username>, with a small "via" badge that names your marketplace.

You need the ratings scope and write on the key. New keys get ratings by default. A key you made before ratings existed keeps the scopes it was made with, so make a new key to rate (see Platform scopes).

Who can rate, and when

• Both sides rate each other: the buyer rates the seller, the seller rates the buyer.
• Only a completed deal: every part released, refunded or cancelled, with at least one released. While any part still holds money or is disputed, the answer is 409 NOT_RATEABLE. A deal where every paid part was refunded ends cancelled and cannot be rated.
• One rating per side per deal, never per milestone. Ratings cannot be changed or taken back.
• There is no deadline.

Two ways in, first wins

You can rate for a side, or the person rates on RekberPay (Pengaturan > Partner Terhubung, Settings, Connected partners). Whichever arrives first counts. The other gets 409 ALREADY_RATED.

curl -X POST "https://api.rekberpay.com/v1/enterprise/platform/deals/3e4f5a6b-7c8d-4e9f-a0b1-c2d3e4f5a6b7/ratings" \
  -H "Authorization: Bearer $REKBERPAY_WORKSPACE_KEY" \
  -H "Idempotency-Key: $(uuidgen | tr 'A-Z' 'a-z')" \
  -H "Content-Type: application/json" \
  -d '{ "rater": "buyer", "stars": 5, "review": "Fast shipping, exactly as described." }'

You name the side (rater), never a user: RekberPay rates the other side of that deal. The side's person must still be linked to you (404 otherwise) and able to act (422 USER_NOT_AVAILABLE for a suspended or closed account).

Blind publication and the 3 day rule

A new rating is private. Nobody sees its stars or review, not even you, until:

• the other side rates too: both publish at the same moment, so neither can answer the other; or
• 3 days pass: RekberPay publishes it on its own.

Get a deal's ratings shows who has rated (submitted: true) and each rating once it is published.

Webhooks

Event	When
rating.created	A side rated. Refs only: no stars, no review
rating.published	The rating is public, with stars, review and published_at
rating.hidden	RekberPay hid or removed the rating. No reason is sent

rating.published can arrive more than once for the same rating: again after RekberPay corrects a rating or shows a hidden one again. Upsert by rating_id.

The public profile

Published ratings from your deals count toward the person's average, rating count and completed deals on RekberPay, exactly like a direct rekber. Each review from a partner deal shows "via [your marketplace name]". There is one reputation, so your users bring theirs with them, and keep it.

Unclaimed accounts

An account you created that the owner has not claimed yet has no public profile: rekberpay.com/u/<username> answers not found, it is not listed on /u, and when it rates someone the review shows "Pengguna RekberPay" without a username. Its ratings still count toward the other person's average, and you can always read its reputation through the API.

If your users already agreed to it, a workspace admin can turn on Show public profiles for accounts not claimed yet in the dashboard (Settings, Public profiles), by ticking the consent statement. The accounts you created then appear at once; turning it off hides them again at once. Every change is recorded with who made it, and RekberPay may change it too. Claimed accounts always follow the normal public rules, whatever the setting, and sandbox accounts never appear.

Reading a reputation

Get a user's reputation (scope users) gives a linked user's average, count, completed deals and 10 latest reviews: the same numbers as their public profile. profile_url is null while the user has no public profile.

Sandbox

Sandbox ratings work end to end: the same rules, the same blind publication (also after 3 days) and the same webhooks, with livemode: false. They never reach a public profile, and a sandbox reputation read counts only your own test ratings and test deals.

Moderation

RekberPay can hide a rating that breaks the rules (for example abusive words), and show it again. A hidden rating leaves the public profile and your API reads, and you get rating.hidden. If RekberPay sees a rating farm, it may hide every rating from your deals at once and freeze your Platform access.

Checklist

• Rate only after the deal is completed; listen for the last milestone.released.
• Treat ALREADY_RATED as done: the person rated on RekberPay first.
• Store ratings by rating_id and update them on every rating.published and rating.hidden.
• Never show the stars before rating.published.

Next steps

• Ratings reference
• Create and link users