Launch regulated payment products on one audit trail

Build a regulated payment product on one SDK. Conjoin logs each verification, charge, and tax calculation to the same audit trail, while your licensed payment processor holds the funds.

Get early access Explore the platform

Answer an auditor from one audit trail

For any transaction, an auditor can ask for the verified user, the calling service, and the approver behind it. When sign-in, billing, and tax come from separate vendors, your team will have to assemble each answer from separate logs, whereas Conjoin records all of those events in one audit trail under the same user ID.

The payment stack, from sign-up to payout

The Conjoin services that verify users, store records, collect payments, and score risk all write to one audit trail.

Sign users up at the verification tier that each account needs

New users sign up through Conjoin Auth, where a user with a verified email address and phone number can open a low-risk account. For a user who moves money, Auth adds a check from the identity verification provider that you connect and records the tier that the user reaches. Your services call one another with machine-to-machine tokens from Auth, which identify the calling service on every request. Because Billing and the other Conjoin services check the user's tier in Auth, your code keeps one copy of each user's verification state.

Outcome

The audit trail links each transaction to the verified user who starts it and the service that sends the request.

Separate payment records from application data

Conjoin Billing stores the transaction history, payout schedules, and invoices, while Conjoin Database stores accounts and the rest of your application data, with field-level encryption on the sensitive columns. Your app uploads statements, tax forms, and identity documents to Conjoin Storage in the region that you choose and shares each one through a signed URL. When Billing sends a webhook for a charge, a refund, or a payout, your backend publishes the event to Conjoin Relay, which delivers it to your risk dashboard, your notification service, and your operations console.

Outcome

Every payment record is in Billing, so your auditors have one place to examine them.

Charge customers and confirm every payment

Conjoin Billing takes one-time charges, rebills subscriptions, sends payouts, and calculates tax, routing each transaction to the processor for your billing entity's jurisdiction. When a charge fails, Billing retries it at the intervals that you configure, such as 1, 3, and 7 days after the failure, and emails the customer at each retry. Conjoin Messaging sends payment confirmations and receipts with a delivery log for each one, while the processor's hosted page presents any 3D Secure challenge to the customer.

Outcome

Your regulated processor transfers the money, while Conjoin manages the subscription, the retries, and the receipts around it.

Code your own rules and score account risk

Deploy your firm's own logic, such as regulatory edge cases, allowlists, and rules that differ by country, to Conjoin Runtime. Runtime starts each container with the Conjoin SDK installed and your project credentials loaded, so your code can query Database and call Billing directly. Alongside those rules, Conjoin AI scores the account-level risk signals that you choose, such as a sudden change in an account's activity.

Outcome

Your processor checks each card payment for fraud, while Conjoin AI flags the account-level risks that your product defines.

The period-end close on Conjoin

At the end of each period, your finance team can reconcile charges, payouts, and tax from the records in Billing, which Conjoin logs in the same audit trail as every sign-in and verification.

One provider

covers split payouts, disputes, and tax

One audit trail

from verification to payout

One API

across the payment processors that Billing supports

What an auditor can trace on Conjoin

Conjoin provides verification, billing, tax, and risk review as separate services, so you can combine only the ones that your product needs.

Verification tiers in Auth

Auth includes the user's verification tier in the session token, so your API can accept a payout request only from an account at the tier that you require.

Transaction records in Conjoin Billing

Your code can query invoices, subscriptions, and payouts through the Billing API at any point in the billing cycle.

Account-level risk review

A Conjoin AI workflow can classify each new account event and pause a payout at an approval step until a person on your team reviews it.

Live events for risk and operations

Relay broadcasts billing, sign-in, and application events to subscribed dashboards and alerting tools in under 50ms.

Your rules on Runtime

Runtime executes your adjudication and regulatory rules in isolated containers and streams their logs to you in real time.

Tax by jurisdiction

Billing calculates tax by jurisdiction, including compound taxes and reverse charges on cross-border sales, and records a breakdown of the rates on every taxed transaction.

A subscription product and a B2B marketplace

One build bills a recurring subscription, while the other splits each order between a seller and your platform.

Subscription SaaS with international billing

A customer signs up through Conjoin Auth with an emailed link, although a customer who picks the regulated plan also has to pass a check with your identity verification vendor. Once the customer subscribes, Conjoin Billing routes each charge to the processor for your billing entity's jurisdiction, calculates tax from the customer's location, and prorates any upgrade. Your app saves a copy of each PDF invoice from Billing to a Conjoin Storage container and keeps the rest of the product's data in Conjoin Database. When Billing records a payment, Conjoin Relay pushes the event to the customer's in-app dashboard and to your operations tracker. Conjoin Messaging sends a renewal reminder before each billing date, so the customer can update a card before Billing tries to charge it. Meanwhile, Conjoin AI flags any account with repeat chargebacks for your team to review. Finally, code on Conjoin Runtime applies the tax-reporting and disclosure rules of each country where you sell.

What this delivers

Your auditors can follow each subscription from sign-up through every renewal in a single log.

B2B marketplace with delayed and split payouts

Buyers and sellers register through Conjoin Auth, where each seller also verifies its business registration and bank details through a verification vendor that you choose. When a buyer places an order, Conjoin Billing charges the buyer and delays the seller's payout at the processor until fulfillment, then splits the payment into the seller's payout and your platform fee. Conjoin Database stores orders, invoices, and dispute records, including those of sellers who leave the marketplace. Sellers upload product documents to Conjoin Storage, from which buyers download them through links that expire. Before Billing releases a large payout, Conjoin AI scores the seller's trust signals and sends a risky payout to your team for manual review. When an order changes state, a Conjoin Relay pipeline starts the next steps, which include your dispute rules on Conjoin Runtime whenever a buyer opens a dispute. Conjoin Messaging threads each buyer-seller conversation against its order and archives every message with the transaction.

What this delivers

Buyers, sellers, and your finance team all work from the same record of each order and its payouts.

Build your next app on Conjoin

Conjoin will open with a free Build tier, while the pricing page already lists the launch prices for Pro and Business. If you tell us what you're building, we'll talk you through early access.

See pricing Get early access