Collection QR Code for Companies: How It Works and When to Use It

Picture a trade show booth with three companies from one delegation, each collecting at its own pace. Emailing a payment link works for a single deal closed after the show, but it breaks down when a buyer is standing at the booth ready to pay and the only device on hand is a phone. That is the problem a collection QR code solves: the buyer is right there, and the payment closes by scanning, with no account number to read aloud and no link to hunt for in an inbox.

At Soulbit Academy we already covered the remote side of collections in what a payment link is and how to collect from abroad. This article covers the other half of the same product family: the collection QR code, built for the moment a payer is physically present. The collection QR code is part of Soulbit V1, confirmed as available today. Here is how it works, what data it carries, when it beats a payment link, and the operational mistakes that trip up companies using it for the first time.

What a collection QR code is and how it works

A collection QR code is a code a company generates from its account and shows to a client who is present, so the client scans it and pays on the spot. The client opens the phone camera, points it at the code, sees the amount, and confirms payment in stablecoin, USDC or USDT. There is no terminal to install and no balance to preload before selling.

The code is generated the same way a payment link is, from the company's account dashboard, and can be tied to an amount and, where it applies, to a sale or invoice reference. The difference from a link is not the underlying technology, it is the channel: a link travels to a distant client, a QR code is shown in person. The transaction is recorded on the network with a unique identifier, verifiable independently of a bank statement, the same record any payment link collection already produces.

Does the seller need special hardware to display the code?

No. The code shows on a phone screen, a tablet, or even printed paper, and the client scans it with their own phone camera. There is no dedicated optical scanner or certified point of sale terminal required. That simplicity is exactly what makes it useful at a booth or a counter where sales volume does not justify installing extra hardware.

When a collection QR code beats a payment link, and when it does not

A collection QR code wins when the client is present and the payment can close on the spot. A payment link wins when the client is somewhere else and the collection has to happen remotely. That difference in channel, not in technology, decides which one to use.

A retail counter, a trade show booth, or an office visit to a client's headquarters are scenarios where the payer is right there: the code resolves the collection without friction, since it needs no shared account number and no wait for the client to open a link on their own device, at a different time and place. An invoice sent to a client in another country is the opposite case: there is nobody present to scan anything, so a payment link remains the right instrument, as covered in the international collections guide.

Collection scenario	Collection QR code	Payment link
Where the payer is	Present, at the same counter, booth, or meeting	Somewhere else, typically remote
How the payment arrives	The client scans the code with a phone camera	The client opens a link sent by email or message
Transaction amount	Works best with an amount set before showing the code	Works equally well for a fixed or open amount
Typical timing	A one time collection that closes on the spot	An invoice the client pays when checking email
Common example	Retail counter, trade show booth, client visit	Invoice sent to a client abroad or in another city

Where a collection QR code fits a company that collects internationally

A collection QR code fits any moment when a company collects with the buyer physically present, even when that buyer is a client visiting from abroad rather than a local customer. Four scenarios cover most cases.

At a retail counter or storefront, the code replaces a card terminal for a client who already holds a stablecoin balance, with no extra hardware to install. At a trade show or an industry event, the same code displays at a booth and covers several collections in a row throughout the day. On a client visit, a sales rep closing a deal at a client's office can show the code from their own phone at the end of the meeting, with no dependence on the client checking email at that exact moment. And on a printed invoice or a physical document, the code can appear alongside traditional bank details as an extra payment option for a client who prefers not to transcribe an account number.

Across all four, what changes is the sales context, not the underlying mechanism: the client scans, confirms payment in stablecoin, and the transaction lands on-chain for the accounting team to reconcile afterward.

What data a collection QR code carries and why it matters for reconciliation

A collection QR code carries, at minimum, an identifier for the merchant receiving the payment and a reference for the transaction that sets it apart from any other. That reference is the piece that makes it possible to reconcile the collection against the invoice later, without manually reviewing every transaction.

EMVCo, the body that defines the QR code payment specifications used by major payment schemes worldwide, distinguishes between a merchant presented QR code, generated by the business for the client to scan, and a consumer presented QR code, generated by the client for the business to read, as EMVCo documents. In Colombia, the Banco de la República's regulation on interoperability for immediate low value payment systems requires that QR codes, whether generated once with a fixed amount or generated fresh for each transaction, carry a merchant identifier and a reference that allows the transaction to be traced, as set out in External Circular DSP-465, carried in Bulletin 33 of 2025 from the Banco de la República, as of August 2026.

That reference is exactly what an accounting team needs to match the collection against the invoice number, the gross amount, and the sale date, without depending on a seller remembering which transaction matched which payment received that day.

QR code field	What it is	Why it matters for reconciliation
Merchant identifier	The identifier of the business receiving the payment	Confirms who collected, without relying on a handwritten name
Transaction reference	A reference specific to that sale or invoice	Tells one collection apart from another on a busy day
Transaction amount	The amount due, if the code was generated with a fixed value	Prevents the client from entering a different amount than agreed
Code type	Generated once, or generated fresh for each transaction	Determines whether an extra reference is needed per collection

Common operational mistakes when collecting with a QR code

The most frequent mistake is reusing the same code across several transactions without changing the reference. A code meant for a single sale that stays taped to the counter for weeks mixes many payments under one identifier, and the accounting team ends up reconciling by hand against the day's register, exactly the manual work the code was supposed to remove.

What other mistakes undermine reconciliation of a QR code collection?

The second mistake is generating the code with an open amount when the sale price is already known. Letting the client type in the amount adds a manual verification step that a fixed amount code does not need. The third is failing to verify the network and the asset before treating a collection as closed: confirming the payment landed in the expected stablecoin, not a different asset, avoids disputes that get harder to resolve once the client has already left the counter or the booth. The fourth is not training the whole sales team on the procedure, so only one person knows how to generate the right code for each transaction, which creates a bottleneck exactly when traffic peaks, such as a trade show with several booths collecting at once.

None of these mistakes are unique to the technology behind the code. They are the same operational lapses that hit any new collection method introduced at a point of sale without a written procedure.

A collection QR code alongside a payment link, not instead of it

A collection QR code and a payment link are not competing tools. They cover different moments of the same collection cycle, and a company that sells both in person and remotely typically needs both.

Should a company that already uses payment links bother adding a collection QR code?

Yes, if any part of its sales happen with a buyer physically present, such as a trade show booth abroad or a client office visit. The two mechanisms share the same underlying account, the same stablecoin settlement, and the same on-chain record, so adding a collection QR code does not mean building a second system. It means covering the in person half of collections that a link, built for a distant client, was never meant to solve.

What Soulbit V1 delivers for collection QR codes, and what it does not

Soulbit V1 generates the collection QR code from the company's account, receives the payment in stablecoin, and confirms the transaction on-chain, with institutional custody while the balance sits in the account. If the company requests it, the balance converts to Colombian pesos through the local banking rail, with the quote visible before confirming. To operate, the company first completes KYB, the verification of the legal entity and its representatives.

What V1 does not deliver is a certified point of sale terminal, direct integration with a register or inventory system, or a dedicated optical scanner: scanning depends on the client's own phone camera, as with any QR code payment. It also does not offer yield, cards or a native token, nor a native app until it reaches the stores. Outside Colombia, the platform settles in stablecoins, USDC and USDT, and in fiat limited to USD, EUR, and GBP; final conversion to local currency outside Colombia stays with the company and its own bank. The full picture of Soulbit's three product legs is in what Soulbit is and how it works, and how each collection gets booked is covered in reconciling stablecoin payments in accounting. The case of an agency already collecting USDC from a US client, with the same kind of on-chain record a QR code produces, is documented in this case study, and the stablecoin behind these collections is covered in what USDC is and how it works for companies. Companies evaluating a collection QR code alongside the rest of the operation can find it in solutions for SMBs.