Fintech Platform Client Workspace Setup (Onboarding)

Fintech Platform Client Workspace Setup (Onboarding)

1. 01

   Confirm the contracted tier before touching the admin panel

   Starter at 1,900 €/mo caps the workspace at 1,000 end-users and 1,000 automation runs per month; Growth at 4,700 €/mo removes both caps. If the client's projected account volume exceeds 1,000, the workspace must be provisioned on Growth or the end-user ceiling will block onboarding mid-delivery.

2. 02

   Provision the white-label front office and bind the client domain

   Load the client's logos, colors, and content into the front office, then attach the custom domain. This is the step that makes the neobank read as the client's own product rather than an agency reseller arrangement, so get sign-off on brand assets before the domain goes live.

3. 03

   Map KYC/AML workflows to the client's actual customer segments

   The platform ships compliance automation, but the trigger logic is yours to define. Walk the client through which document sets, verification thresholds, and review queues apply to retail versus entity accounts, then configure the automation builder to route each segment correctly.

4. 04

   Wire IBAN account provisioning and debit card issuance

   Connect the account management module so new verified users receive IBAN accounts automatically, and configure card issuing rules (spend limits, card types, activation flow). Test one full path from signup through first transaction before opening to real users.

5. 05

   Build the transaction monitoring dashboard the client will actually read

   Set the alert thresholds and reporting views the client's ops team needs for daily oversight. A monitoring dashboard nobody opens is a compliance gap, so agree on which events trigger a notification and who receives it.

6. 06

   Run a compliance reporting dry run with the client's team

   Generate a sample report from the platform and have the client's designated compliance contact walk through it. This surfaces gaps in workflow configuration while the agency is still in the 60-hour setup window rather than after go-live.

7. 07

   Hand over admin access and document the retainer scope

   Train the client team on platform administration, then define what the 10h/mo ongoing retainer covers: automation tuning, workflow updates, and reporting support. Anything outside that scope becomes a change order.