Every product that moves money sits on top of a regulated bank, and that bank is responsible for what you build.
Your bank partner holds the charter, answers to regulators and carries the final responsibility for anti-money laundering, sanctions and consumer protection. You build the product and run the day to day controls. A compliance program is the written agreement, in practice, about how those two halves fit together.
Here is how to build one that your bank trusts and your team can actually run.
1. Agree on who owns what
Before writing a single policy, map every obligation to an owner. Typical splits look like this:
- Customer identification: You collect and verify identity; the bank approves the process and audits it.
- Transaction monitoring: You run alerts and first level reviews; the bank reviews escalations and files suspicious activity reports.
- Sanctions screening: Usually shared, with screening at onboarding and on every payment.
- Complaints: You handle them; the bank receives regular reports and reviews trends.
Write it down. Most problems in bank partnerships start with an obligation everyone assumed someone else owned.
2. Write policies you will follow
Your bank will ask for policies covering anti-money laundering, customer identification, sanctions, fraud, complaints and vendor management. Keep them short and specific to your product. A ten page policy your team follows beats a hundred page template nobody reads.
3. Know your customers, then keep knowing them
Onboarding checks are only the start. Set rules for when a customer must be reviewed again: a large jump in volume, a new country, a change in business type. Record every decision with the reason behind it.
4. Monitor transactions with clear thresholds
Start with simple, explainable rules: unusual amounts, rapid movement of funds in and out, payments to high risk regions. Tune them monthly. Your bank will want to see how many alerts you raise, how fast you close them and how many you escalate.
5. Train the team
Everyone who touches customers or payments needs annual training on spotting financial crime, and support staff need to know how to escalate a concern. Keep attendance records; examiners ask for them.
6. Prepare for reviews before they are announced
Your bank will review your program at least once a year, and regulators may review the bank’s oversight of you. Keep a single folder with current policies, the ownership map, monitoring metrics, training records and the findings from the last review with their fixes.
7. Report regularly, not only when something breaks
Send your bank a monthly report: new customers, volumes, alerts, complaints and any incidents. Partners who hear from you often trust you more when something does go wrong.
How Backspin helps
Backspin gives you identity verification, sanctions screening and transaction monitoring through the same API you use to move money, with case management in the dashboard and exportable reports your bank partner can review directly. You still own your program; we make sure the evidence is always one click away.
A strong compliance program is not a cost of launching. It is what lets you keep growing once you have.
