> ## Documentation Index > Fetch the complete documentation index at: https://docs.fluz.app/llms.txt > Use this file to discover all available pages before exploring further. # User journey review > If your application onboards and verifies its own customers, or puts Fluz cards in their hands, our risk review team reviews your user journey before you go live. Here's what to submit and the rules the program runs on. Fluz lets platforms bring their own customers. You can register them through the API, submit the identity verification you already run, and issue cards and move money for them, all without asking them to start over with us. When you do that, your sign-up flow becomes part of a regulated program that Fluz runs with its sponsor banks and card networks. So before you go live, the Fluz risk review team reviews the journey your customer takes, from the first screen to the first transaction. We need it on file, and we need it to match what your customers actually see. > [!NOTE] > > **You don't have to wait to build.** Staging stays open while your review is in progress. Most platforms finish the integration in parallel and go live once their journey is approved. ## When you need a review You need an approved user journey before going live if your application does any of the following: * Registers users or businesses on Fluz through the API, with [user registration](https://docs.fluz.app/user-registration.md) or [business registration](https://docs.fluz.app/kyb-overview.md). * Submits KYC or KYB from your own provider with [Verify by external provider](https://docs.fluz.app/verify-customers-by-external-provider.md). * Issues cards, holds balances, or sends payouts for your own customers. * Changes a journey we've already approved, such as a new onboarding screen, a new country, a new customer type, a new funding method or a new distribution partner. If you only use Fluz for your own business's spend, this page doesn't apply. > [!WARNING] > > **Cards on your business account are for your business.** If your customers will use cards issued on your account, that is a sub-program, and it needs sponsor bank approval before you build it. Tell us in your submission so we can start that approval early. ## How the review works **1. Contact the risk review team** Email [partnerships@fluz.app](mailto:partnerships@fluz.app) with the subject **User journey review – your application name**, or ask your implementation lead in your shared Slack channel. We'll open the review and confirm who on our side owns it. If you're a money services business, gaming operator or another [specialized vertical](https://docs.fluz.app/specialized-verticals.md), complete that review form too. The two reviews run together. **2. Submit your user journey** Send the full package described below in one place, a single document or shared folder. Pieces spread across email threads slow the review down. **3. Walk us through it** We'll schedule a call where you take us through the journey in staging, the way a new customer would see it. This is a working session. Most of the open questions get answered here. **4. Follow-ups and partner alignment** Expect follow-ups on verification, disclosures and funds flow. Where the program requires it, we align with our sponsor bank, processor or card network. This step is largely out of your hands. **5. Approval for the journey as submitted** We approve the journey you submitted and enable the production capabilities it needs on your application, such as `VERIFY_KYC` for external provider results and the card offers for your program. > [!NOTE] > > Approval covers the journey as you described it. If it changes later, come back to us first. Changes are reviewed, but they're a conversation, not a restart. ## What to submit The more specific the package, the faster the review. Show us what your customer will actually see and do, not what the product might do someday. | Item | What we need | | :- | :- | | **Screens** | Every screen from first visit to first transaction, in order, on web and mobile, as customers will see them in production. Screenshots or a screen recording. | | **Where you offer it** | The website URLs and app store listings where you market the service powered by Fluz. These must match the website or app URL on your [developer application](https://docs.fluz.app/fluz-dashboard/application-scopes.md). | | **Who your customers are** | Consumers, businesses or both; their countries of residence; how you acquire them (your own marketing, partners, agents); and projected customers, cards and monthly spend for the first 12 months. | | **How you verify identity** | Your provider; the data you collect (name, date of birth, address, SSN or ID number, document, selfie); your pass and fail rules; and how you handle failures, duplicates, account recovery and re-verification. Include your CIP policy. | | **Disclosures and consent** | Where the Fluz and sponsor bank terms appear, the exact wording, how acceptance is captured (checkbox, timestamp, terms version) and how long you keep that record. Show where the Fluz consent screen sits in the flow. | | **Funds flow** | A diagram showing where money comes from, which account holds it, who uses the card or receives the payout, and how refunds and returns flow back. | | **Card use** | Who holds each card, whose name and address it carries, and what it will be used for. | | **Your compliance program** | Your AML policy, sanctions screening, transaction monitoring, prohibited countries and businesses, complaints handling and marketing review. Include your licenses and registrations, such as FinCEN MSB registration. | | **Everyone else in the path** | Any partner, agent, reseller or other platform between you and your customer. If there are none, say so. | ## Program requirements These apply to every program that onboards its own customers. Build them into your journey. We review against them before launch and monitor against them after. ### Every card belongs to a verified person Each card a customer uses carries that customer's own verified name and address, on their own Fluz account. Cards on your business account carry your business's details and are for your business's own use, unless an approved sub-program covers them. ### Cards and accounts stay with the customer Card numbers, card details and account access go only to the verified cardholder. They can't be sold, transferred or handed to anyone else, and your customer terms should say so. Showing cards through the Fluz [card reveal](https://docs.fluz.app/build-a-platform/card-reveal.md) element keeps card data off your servers. ### Your customers, on your platform Offer the services you build on Fluz only to your own customers, through the application and URLs in your approved journey. Offering them through another platform, an agent network or a reseller needs our written approval first. ### Each customer approves your application once A customer grants your application access to their Fluz account once, through the Fluz consent screen, at onboarding. After that you act for them with [user access tokens](https://docs.fluz.app/recipes/generate-user-access-token.md) and they aren't sent back to Fluz. The customer stays the owner of their account, and the approval is what lets you act on it. ### We receive the verification you relied on For each customer you verify, send the full decisioned result: identity data, document and selfie evidence where you collected it, and the date your provider made the decision. A pass on its own isn't enough. Results more than 100 days old aren't accepted. When we ask for more on a customer, answer within the time given in the request. ### Fund the way you described Customers fund from accounts and cards in their own name. Only the funding methods in your approved solution design are enabled. Adding another method, including digital assets, is a change that comes back to review. ### Serve the markets you were approved for Cards on a customer's own account require a US address. Customers outside the US can be served only through a model approved for them. Market only in the countries in your approved journey. Cards are blocked in restricted countries. ### Describe Fluz and the bank accurately Use the disclosure language we approve with you. Name the sponsor bank as it appears in the card terms, describe deposit insurance only in the approved wording, and don't present the Fluz or bank terms as anything other than what's published at [fluz.app/us/legal](https://fluz.app/us/legal/). ### Keep your books matched to ours If you hold balances or cards for customers on your own account, keep a ledger by customer and by card, and reconcile it daily against the [transactions API](https://docs.fluz.app/features/get-all-transactions.md). Webhooks alone aren't a reconciliation. ### Monitor, and tell us early Run your own transaction monitoring and sanctions screening, and tell us promptly when you see activity that doesn't fit your journey. Fluz also monitors card issuance, geography and merchant mix against the projections you gave us. When activity moves outside them, expect a request for information, and card issuance may be limited until it's answered. ### Changes come to us first Give us at least 30 days' notice before a material change to your journey, customers, markets, funding or distribution. The change goes live once we confirm it. ## If activity doesn't match the journey If what we see in production doesn't match the journey you submitted, we may pause card issuance or limit your application while we review it with you. A pause is a review step. The fastest way through it is a quick, complete answer. ## Start the review > [card] [Ready to submit?](mailto:partnerships@fluz.app) > > Email [partnerships@fluz.app](mailto:partnerships@fluz.app) with the subject **User journey review – your application name**, or reach your implementation lead in your shared Slack channel. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.