Back to work / Philcoin

Case 03 · Commissions · Polygon claims

Ambassador Program

Ambassadors earn referral commissions and claim tokens on Polygon.

Ambassadors earn commissions when their referral network buys PRO or promotes posts. I built commission accounting and the Polygon claim pipeline: eligibility checks, balance reservation, AWS KMS-signed ERC-20 transfers and receipt reconciliation, plus member and admin interfaces.

Result

Backend and backoffice API in production since September 2026, including Polygon treasury claims. Member and admin interfaces delivered to development.

01

Blockchain claim pipeline

Built Polygon ERC-20 treasury payouts with AWS KMS signing, transaction tracking and receipt reconciliation.

02

Payout correctness

Reserved balances, serialized nonce allocation for concurrent claims and released earnings after failed broadcasts.

03

Commissions & interfaces

Built referral attribution, the commission ledger, member claim views and administrative tooling.

How it worksSimplified walkthrough. No live transactions.

From referral commission to an on-chain claim payment

PRO / promoted posts + referral network

A referral buys PRO or boosts a post. The backend attributes the purchase and records the ambassador’s commission.

PRO or boost purchase → ambassador commissionEach commission traces back to a qualifying purchase.
Example state, not live data
Ledger
Accrued
Transfer
Not submitted
Member view
Earnings

Off-chain accounting, on-chain payment

Commissions accrue in PostgreSQL. A claim settles through an ERC-20 treasury transfer on Polygon, signed with AWS KMS.

Handle transaction failures

Balance reservation, nonce serialization and receipt reconciliation connect financial accounting to the actual transaction lifecycle.

Blockchain implementation

Claim API → KMS signer → Polygon receipt

The walkthrough documents treasury settlement, concurrent-claim handling and failed-broadcast recovery from the implementation records.

Release scope

Backend shipped; interfaces in development

September release records distinguish deployed APIs from the development-stage member and admin screens.

Status follows the September 2026 implementation and release records. Ambassador appointment is managed through the backoffice.

Built with

Backend and backoffice API in production; member and administrative screens delivered to development.

Email meNext case: PHL → GIVE Swap