Recurring B2B Payments: How to Set Them Up in Stablecoin

A data consultancy in Lima bills a fixed monthly retainer to a client in Chicago. The contract is signed, the amount does not change month to month. The operational question shows up on day one of every cycle: how to collect that same amount from that same client without rebuilding the collection process from scratch each time, and without opening a US bank account just to set up a recurring debit.

At Soulbit Academy we treat a recurring payment as what it actually is in practice: a process that repeats, not necessarily a charge that runs by itself. Soulbit is a stablecoin payments and treasury rail for companies, and its V1 lets a company set up a recurring collection with payment links and collection QR codes reissued every cycle. Institutional stablecoin adoption in cross-border payments sits around 71% in Latin America, according to industry reports, which explains why agencies, consultancies, and subscription businesses across the region already evaluate this mechanism for their recurring revenue. This article covers the difference between an instrumented recurring collection and an automatic bank debit, and walks through the full operating cycle, from generating the link to invoicing each period.

What a recurring B2B payment is, and what it is not

A recurring B2B payment is a charge a company repeats on a fixed cycle, to the same client, for the same item; it is not necessarily an automatic charge that runs without anyone stepping in. An agency with a monthly retainer, a software company with an annual subscription, and a trade association with a quarterly membership fee are all the same pattern: the cycle and the billed item repeat, even though the technical instrument that executes the collection can differ a lot from one case to the next.

That technical instrument splits two models that get confused often. The first is the automatic charge, where the client authorizes once and the collection runs on its own every following cycle, with no one repeating any action. The second is the instrumented recurring collection, where the company reissues a collection mechanism, such as a payment link or a QR code, every period, and the client confirms payment each time. Both solve the same business problem, revenue that repeats, with a different operating mechanic.

Does a recurring stablecoin collection work the same as an automatic bank debit?

No. An automatic bank debit, sometimes called a preauthorized transfer, runs without the client repeating any action after the initial authorization. A recurring collection under Soulbit V1 requires the company to generate a new link or QR code every cycle, and the client to open it and pay. It is a real recurring collection, but an instrumented one, not an automatic charge.

Instrumented recurring collection versus an automatic bank debit

The difference between an instrumented recurring collection and an automatic bank debit sits in who acts on every cycle, not in whether the revenue itself is recurring.

An automatic bank debit asks for a single authorization, almost always signed or confirmed in writing, and from there the bank or the card issuer runs the charge on its own, cycle after cycle, until the client cancels it. In the United States, that authorization has to meet the requirements Regulation E sets for preauthorized electronic fund transfers, including written or similarly authenticated consent and a copy of the terms given to the client. An instrumented recurring collection with a payment link or QR code flips that logic: the company sends a new collection mechanism every cycle, and the payment only runs once the client decides to open it and confirm.

Dimension	Automatic bank debit	Instrumented recurring collection in Soulbit
Client action every cycle	None, after the initial authorization	Open the link or scan the QR code and confirm payment
Risk of a missed cycle	Low for the client, high if the account lacks funds	Depends on the client remembering to pay each period
Upfront setup	Signed authorization, tied to an account or card	None: every link stands on its own
Asset the company receives	Fiat currency, per the bank or the processor	Stablecoins such as USDC or USDT
Available in Soulbit V1	Not offered in stablecoin within the product	Available today with payment links and collection QR codes

How to set up a recurring collection with a payment link or QR code

Setting up a recurring collection with a payment link or QR code follows the same cycle every period, from generating it to reconciling the payment against the invoice.

First, the company and the client agree on the amount and the cycle, for example a monthly retainer or a quarterly subscription. Second, at the start of each cycle, the company generates a new payment link or a new QR code from its account and ties it to that period's amount. Third, it shares the link or the code with the client, by email, message, or alongside that period's invoice. Fourth, the client opens the link or scans the code and pays in stablecoin, USDC or USDT, from their own account. Fifth, the transaction gets recorded with a unique identifier and, if the company requests it, the balance converts to local currency. Sixth, the accounting team reconciles that identifier against the invoice for that specific cycle.

Does a company need to generate a new link every month even if the client and the amount stay the same?

Yes. Under Soulbit V1, every cycle needs its own payment link or QR code, even when the client and the amount are identical to the previous cycle. The system does not reuse the same link automatically from one period to the next, nor does it schedule the send on its own: generating and sharing it is a step the company repeats every cycle.

For a one-off, non-repeating collection, the same underlying mechanism is covered in detail in what a payment link is for international collections and in how a collection QR code works for companies. The mechanics underneath, generate, share, collect, and reconcile, are the same. What changes in a recurring payment is that this cycle repeats every period, instead of happening once.

Step	What happens every cycle	Who repeats it
1. Generate the link or QR	The company creates it and ties it to that period's amount	The company, every cycle
2. Share the link	Sent by email, message, or alongside the invoice	The company, every cycle
3. The client pays	Opens the link or scans the QR and confirms in USDC or USDT	The client, every cycle
4. On-chain confirmation	The network records the transaction with a unique identifier	Automatic, no manual step
5. Reconciliation	The identifier gets matched against that period's invoice	The accounting team, every cycle

What happens when a recurring cycle runs late or the client does not pay

An instrumented recurring cycle simply stays pending if the client does not open the link or scan the QR code in time, because there is no automatic retry that runs on its own.

That is the main operating difference from an automatic bank debit, where the bank retries the charge under its own rules. With a payment link or QR code, following up on a late cycle falls on the company: a reminder by email or message, a second copy of the link, or a call if the delay repeats. For a company with dozens of recurring clients, that manual follow up needs a defined process, with clear owners and deadlines for escalating an overdue cycle before it turns into churn. The internal controls a company already uses to approve its own outgoing payments are a useful starting point for designing that same discipline in reverse, as a collector: internal controls for payment approval walks through that same logic of owners and deadlines applied to payments, and it carries over to collections.

The underlying risk is the same one any subscription business faces: a cycle not collected on time strains cash flow before it turns into an actual lost client. An instrumented recurring collection does not remove that risk, it makes it more visible, because every cycle requires an explicit action instead of running silently in the background.

Invoicing and reconciling recurring revenue collected in stablecoin

Every cycle of a recurring payment still requires its own invoice, regardless of whether the collection instrument is a stablecoin payment link.

Colombia's DIAN Resolution 000165 of 2023 sets the country's electronic invoicing system and requires an invoice for every sale operation. That requirement does not distinguish between a one-off collection and one that repeats every month to the same client: every recurring cycle needs its own invoice, with the billed period clearly identified. The collection instrument, bank transfer, card, or stablecoin, does not change that tax requirement.

The cost of collecting a retainer from abroad through a repeated bank wire every month also factors into the decision. The average cost of a cross-border money transfer reached 6.36% in the third quarter of 2025, according to the World Bank's Remittance Prices Worldwide report. That figure measures remittances rather than B2B collections, but it illustrates the structural cost of repeating an international transfer every cycle, the same problem a recurring stablecoin collection aims to reduce. Reconciling each cycle, matching the on-chain identifier against the invoice, follows the same process as any other stablecoin collection, covered in full in reconciling stablecoin payments in accounting.

What Soulbit V1 delivers for recurring collections, and what it does not

Soulbit V1 delivers the collection side: generating a payment link or a QR code every cycle, receiving the on-chain confirmation, and, if the company requests it, converting the balance to pesos through the local banking rail in Colombia, with institutional custody while the balance sits in the account.

What it does not deliver today is automating the charge itself. There is no automatic bank debit in stablecoin, no recurring card charge, and no scheduled retry that runs without the company reissuing the link or the QR code every cycle. It also does not offer yield on balances, spending cards, or a native token. The company remains responsible for invoicing every cycle and for manually following up on late collections. The full picture of the product is in what Soulbit is and how it works.

Does Soulbit plan to automate recurring collections in the future?

Automating recurring collection depends on product decisions that are not settled yet. This article describes only what V1 delivers today: an instrumented recurring collection with a payment link and a QR code, not an automatic charge. Any future change gets documented once it is confirmed and available, not before.

Who this model fits today

An instrumented recurring collection fits best for businesses with a small number of recurring clients and a high amount per cycle, where the manual step of reissuing the link every period weighs little against the total collected.

An agency with monthly retainers from a handful of large clients, a consultancy with fixed quarterly fees, or an early-stage software company with a small number of enterprise accounts are the profiles where this model works best today. The case of a SaaS startup collecting USDC from clients in twelve countries, documented in this case study, shows how the same mechanism scales as the number of recurring accounts grows, even though every cycle still requires its own link. For a mass subscription business with thousands of small collections per cycle, the manual step of reissuing every link weighs too much, and the traditional banking circuit with an automatic debit remains the more efficient tool while that mechanism does not exist in stablecoin.