Loading, please wait…
Participant profiles serve as the system of record for businesses and individuals operating within your platform ecosystem.
A participant profile contains the information required to onboard, verify, activate, manage, and support a participant across enabled platform services. Once created, the same profile can be reused across payments, payouts, embedded finance, reporting, and operational workflows.
Participant profiles should be created once and maintained throughout the participant lifecycle. Changes to participant information are managed through profile updates rather than creating replacement profiles.
Participant profile management helps ensure that participant information remains accurate, consistent, and usable across all enabled platform services.
Effective profile management supports:
Maintaining a single participant profile helps reduce operational complexity and avoids duplicate onboarding activities.
Profile creation establishes the participant record used across the platform ecosystem.
Platform profile creation establishes:
Participant profile creation establishes:
Once created, FFP assigns identifiers that can be used across onboarding, operational, reporting, and financial workflows.
The participant profile may contain multiple categories of information.
| Category | Examples |
|---|---|
| Identity | Legal name, date of birth, tax or identity information |
| Business | Legal business name, registration data, entity type, DBA, MCC, business activity |
| Contact | Email, phone number, preferred language |
| Address | Residential, registered, operational, or mailing address |
| Ownership & Control | Beneficial owners, ownership percentages, control persons, representatives |
| Compliance | Verification status, screening results, documents, review outcomes |
| Financial Accounts | Funding, settlement, payout, bank, card, or wallet information |
| Product Configuration | Enabled services, restrictions, limits, provisioning references |
| Consent | Accepted terms, disclosures, agreements, consent versions |
| Audit History | Timestamps, changes, decisions, reasons, source, actor |
Participant information may change over time and should be maintained using profile updates.
Certain changes may trigger additional review or reverification requirements.
Common examples include:
When updates are required, continue using the existing participant profile.
Do not create replacement profiles to bypass outstanding requirements, reviews, or reverification activities.
Participant profiles continue to be managed after creation.
| Lifecycle Activity | Description |
|---|---|
| Create Profile | Establish participant record |
| Assign Identifiers | Associate platform and service references |
| Update Profile | Maintain current information |
| Review Changes | Evaluate updates requiring additional review |
| Extend Services | Enable new platform capabilities |
| Maintain References | Preserve identifiers across enabled services |
| Track Changes | Retain audit and decision history |
| Support Operations | Support servicing, reporting, and participant management |
When managing participant profiles:
Participant profiles serve as the foundation for multiple platform services.
| Capability | Dependency |
|---|---|
| Payment Acceptance | Participant eligibility and acceptance setup |
| Funds Management | Allocation rules, balances, settlement references |
| Payouts | Verification status, payout destination, eligibility |
| Embedded Finance | Verification, consent, disclosures, product enablement |
| Global Payouts | Recipient information and country-specific requirements |
| Reporting & Operations | Participant visibility, reporting, servicing, audit trails |
Because profile information is centrally maintained, additional capabilities can be enabled without recreating participant records.