AIComplyRemit · 2026

ComplyRemit

A cross-border payments platform with an AI support agent that reads the customer's own account and hands off to a human mid-conversation.

Live site

−94%

Support poll load

Apps, one workspace

API domains

Overview

ComplyRemit moves money across borders, so almost every screen sits on top of KYC, an approval gate, or a payment rail. I built it as a single npm workspace: an Express 5 API on Node 24 with Prisma over PostgreSQL, three Next.js front ends (customer app, operator console, marketing site), a Stripe storefront, and an Expo mobile app covering the same customer journey. Thirteen API domains share that one server — auth, onboarding, recipients, bank accounts, KYC, payments, support, admin and webhooks. The piece I'm proudest of is the support layer: an AI assistant that can actually see the caller's own transfers, and that knows when to stop talking and fetch a person.

Key features

AI support assistant with scoped, read-only tool calling over the caller's own account
Live human handoff — the bot goes silent the moment a conversation is queued
Operator console with a multi-conversation support dock, approval queue and compliance 360
Separate identity systems: hosted auth for customers, first-party JWT for operators
KYC, bank-linked funding and multi-currency payouts behind one API
Expo/React Native app covering the same journey as the web client
Application-level encryption for personal data, including support transcripts

Challenges & solutions

An assistant that can read account data is an IDOR waiting to happen — a customer can talk a model into looking up someone else. So no tool takes a subject at all: every lookup closes over the authenticated session, and a test asserts that no tool parameter is ever named for a user. Prompt wording alone was never going to hold that line.
Two voices answering one customer is what makes people distrust a support widget. The assistant answers only while the conversation is in its bot state and stops completely once a human is queued — and because transcripts are persisted rather than held in React state, the agent who picks it up inherits the whole conversation instead of asking the customer to repeat themselves.
The first cut of live chat polled hard enough to trip production rate limits. Reworking it — one round trip per tick instead of three, and an interval that backs off 2s → 15s as polls come back empty — took an agent with three panels open from roughly 204 requests a minute to about 12 at rest, without adding sockets to a two-instance deployment.
The assistant's prompt is a product claim, and it drifted: an earlier version offered corridors that were never built and described a login flow that had been replaced. Nothing errored — every answer just read fluently and wrong. It's now asserted in tests against the same source of truth the API validates against.

Screenshots

ComplyRemit homepage hero advertising cross-border payments at a 0.3% flat fee — Marketing site — one promise, stated plainly

Three product cards covering payments, treasury management and invoice lending — Three products, one login — payments, treasury, lending

Side-by-side comparison of traditional bank fees against ComplyRemit pricing — Pricing framed as a comparison, not a table

Security section covering insurance, audits, monitoring and licensing — Compliance posture, up front — this is a regulated product

Get in touch section with an early access request form — Early-access capture at the end of the page

Explore more projectsView all

Let's Build Something Amazing Together

Have a product in mind? Let's turn it into something users love — fast, scalable, and beautifully engineered.

Start Your Project

Book a Free Consultation

Loading…

Overview

Key features

AI support assistant with scoped, read-only tool calling over the caller's own account

Live human handoff — the bot goes silent the moment a conversation is queued

Operator console with a multi-conversation support dock, approval queue and compliance 360

Separate identity systems: hosted auth for customers, first-party JWT for operators

KYC, bank-linked funding and multi-currency payouts behind one API

Expo/React Native app covering the same journey as the web client

Application-level encryption for personal data, including support transcripts

Challenges & solutions

An assistant that can read account data is an IDOR waiting to happen — a customer can talk a model into looking up someone else. So no tool takes a subject at all: every lookup closes over the authenticated session, and a test asserts that no tool parameter is ever named for a user. Prompt wording alone was never going to hold that line.

Two voices answering one customer is what makes people distrust a support widget. The assistant answers only while the conversation is in its bot state and stops completely once a human is queued — and because transcripts are persisted rather than held in React state, the agent who picks it up inherits the whole conversation instead of asking the customer to repeat themselves.

The first cut of live chat polled hard enough to trip production rate limits. Reworking it — one round trip per tick instead of three, and an interval that backs off 2s → 15s as polls come back empty — took an agent with three panels open from roughly 204 requests a minute to about 12 at rest, without adding sockets to a two-instance deployment.

The assistant's prompt is a product claim, and it drifted: an earlier version offered corridors that were never built and described a login flow that had been replaced. Nothing errored — every answer just read fluently and wrong. It's now asserted in tests against the same source of truth the API validates against.