Onboarding Participants: The Scheme Membership Lifecycle
It is easy to focus on the payment and forget the participant. But a scheme is a club: before an institution can move real money on it, it has to be let in — and letting members in, safely, is a discipline of its own. That discipline is the membership lifecycle, and it is the backbone of scheme operations.
Sandbox → certified → live
A new participant starts in a sandbox: they can integrate and test against the API without touching production money. When their integration is proven, they are certified — the scheme has verified they handle the message formats, the edge cases, and the failure modes correctly. Only then do they go live and move real value. And because things change, a live participant can be suspended — for risk, for a breach, for maintenance — and later reactivated. Each transition is a deliberate, auditable act.
Limits are part of membership
Membership isn't binary. Each participant carries controls: a per-participant daily limit caps exposure; a type (bank, fintech, PSP) drives which rules apply. These aren't payment-level checks — they are properties of the relationship between the scheme and the participant, and they live with the participant record, not the transaction.
Why it needs its own portal
Participant management is often buried in spreadsheets and email approvals. Pulling it into the platform — where you can see every participant, their status, their limit, and their live volume in one place, and move them through the lifecycle with a click — turns onboarding from a project into an operation. In Kibipay, a participant maps to a tenant; the participant portal is the scheme-operator view of that tenant's membership: onboard, certify, go live, set a limit, suspend, reactivate.
The point
Anyone can accept a payment. Running a network means deciding who may send and receive, under what limits, and in what state — and being able to prove it. The membership lifecycle is how a platform answers the question every regulator eventually asks: who exactly is on your rails, and how did they get there?