Escrow before approval
Separate paying from becoming an approved member, so the contract can represent a purchase awaiting identity verification.
Case 01 · Membership platform
Founders Club
A buyer pays first; the certificate follows identity approval.
I built the frontend, backend and smart contracts that turn a membership purchase into an identity-verified NFT certificate and benefits inside the Phil app.
Result
The purchase, identity verification, certificate minting and treasury-release flow reached Polygon production. Membership benefits connect back to the Phil ecosystem.
My part
What I did
A purchase crosses four systems: wallet, identity verification, membership contract and Phil account. I needed each system to agree on whether the buyer was actually a member.
01
Product interface
Built the purchase experience, wallet connection, account authentication and membership certificate views.
02
Backend & integration
Connected Cognito authentication, Didit identity verification, webhook handling and the Phil API.
03
Smart contracts
Implemented upgradeable membership, escrow, tier upgrades and NFT certificate contracts.
How it worksSimplified walkthrough. No live transactions.
System flow
Wallet + Solidity
The member chooses a tier and pays through the membership contract. For a new buyer, the funds are held while identity verification is pending.
purchaseMembershipPayment recorded; membership is not yet approved.Example state, not live data
- Payment
- In escrow
- Identity
- Pending
- Certificate
- Not issued
Didit + backend
A verified identity-provider webhook updates eligibility. The backend connects the identity decision to the membership and the Phil account.
KYC webhook → eligibilityAn identity decision must reach the correct membership.Example state, not live data
- Payment
- In escrow
- Identity
- Approved
- Certificate
- Pending issuance
Solidity + NFT
After approval, the membership flow releases escrow to the treasury and issues the NFT membership certificate.
approveAndMintThe certificate and settlement follow the approval state.Example state, not live data
- Payment
- Released
- Identity
- Approved
- Certificate
- Issued
Phil API + rewards
Membership state is reflected in the Phil profile. PHL benefits are handled through the rewards service rather than assumed to come from the NFT contract.
Membership → app profile → rewardsThe on-chain purchase becomes a usable product entitlement.Example state, not live data
- Payment
- Released
- Identity
- Approved
- Certificate
- Linked to app
Trade-offs
Decisions I made
Keep membership state in sync
Connect wallet state, identity-provider events, contract events and the Phil profile so the buyer sees the same membership status throughout.
Links and records
See the work
Live productOpen the live Founders product
Public membership portal. No account or wallet is needed to see the entry experience.
On-chain artifactMembership contract on Polygon
Deployed membership address recorded in the production launch.
Case based on the membership implementation and April 2026 production launch records.
The walkthrough explains the implementation. It does not connect a wallet or submit transactions.