A business with several Bolivian locations needs more from QR payment acceptance than a successful scan. It needs to know which branch collected the money, who can view the payment and what happens to the code when a till closes or a service changes.
When comparing payment providers in Bolivia, examine that operating structure alongside customer reach. QR interoperability helps customers pay across institutions; the merchant still needs a collection service that fits its accounts, staff and reporting. BOB payouts require a separate assessment.
Start with interoperable payments, then examine the business service
The Banco Central de Bolivia's January 2026 Financial Stability Report describes a shared, interoperable payments environment, including QR payments across financial institutions. This establishes the local infrastructure context. It does not establish a particular merchant's eligibility or the features of a PSP's commercial service. BCB report, pages 83–85.
Public bank products show why the business layer matters. Banco BISA describes company-managed users, collection into different accounts, QR generation for individual transactions or batches, and reports organised by branches, agencies and cashboxes. These are documented features of its business QR service, not a claim about every Bolivian provider. BISA QR for businesses.
BCP's public Multiplica QR page identifies cashier and agency-manager roles and describes viewing, downloading and reconciling incoming QR credits. That is a useful starting point for a demonstration, rather than proof of a particular permission configuration. BCP Multiplica QR.
These public examples illustrate questions to ask; their inclusion does not identify providers in PayStar's private offer sample or imply a partnership.
Test branch attribution and permissions together
Give the prospective provider your actual organisation chart: legal entity, receiving accounts, locations and staff roles. Ask it to show how that structure appears in the proposed service.
| Business requirement | Demonstration to request |
|---|---|
| Several branches use one receiving account | Trace each credit to the intended branch and till |
| Different business services receive into different accounts | Show who selects the account and who can change it |
| A cashier must confirm today's receipts | Demonstrate the cashier's access without using a shared administrator login |
| Finance needs a daily close | Export transaction records and compare branch totals with account credits |
Treat these as acceptance criteria to agree, not assumed product capabilities. Also ask how access is removed when an employee leaves, whether historical attribution survives a staff change and how corrections appear in later exports. Payment managers need to understand who can change a receiving account as clearly as who can see a receipt.
A balancing total can still hide a branch error
Consider a hypothetical company with two branches sharing one collection account. Branch A records eight orders of BOB 125, totalling BOB 1,000. Branch B records five orders of BOB 200, also totalling BOB 1,000. Together, the expected receipts are BOB 2,000.
Now suppose one BOB 125 customer payment from Branch A uses a code assigned to Branch B. The bank account can still receive the full BOB 2,000 while the branch report shows BOB 875 for A and BOB 1,125 for B. Matching only the account total would miss the attribution error.
Use this invented exercise in the demonstration. Ask what identifies the branch, whether staff can detect the mismatch and how finance records a correction without obscuring the original payment. The amounts are teaching examples, not typical Bolivian tickets or an observed bank defect. A provider may prevent the situation differently; the purpose is to see its actual control.
Include QR retirement in the launch checklist
Printed and shared codes can outlast the campaign or location that created them. BCP's published Multiplica terms state that previously generated codes can remain valid for their assigned period after service termination unless the customer expressly requests otherwise. The terms do not display an effective date, so confirm the applicable version and cancellation process with the bank. Multiplica terms.
For the service you choose, document how to retire a code, replace signs and saved images, and investigate a payment that arrives after the business stops using it. Demonstrate what an old code does after a receiving account or branch changes. Disabling a staff login and cancelling a customer-facing payment instruction should be separate questions in that test.
Qualify BOB payouts and settlement separately
Banco BISA's supplier-payment page describes transfers to its own and other banks' accounts, with scheduled payments and company-defined approval levels. This is a separate business-payment example; QR collection support alone does not establish access to it. BISA supplier payments.
For your payout proposal, specify the recipient type and purpose, funding account, approval roles, limits, fees and evidence of completion. Ask how a rejected transfer or uncertain result is investigated before another instruction is sent. Confirm customer-return procedures separately from supplier payments.
Keep three questions distinct: where a collection is credited, how the merchant receives settlement, and how payouts are funded. Domestic BOB functionality does not by itself establish foreign-merchant eligibility, currency conversion or settlement outside Bolivia. Obtain those terms for your entity and business activity.
Build a focused shortlist with PayStar Discovery
PayStar's 14 September 2026 snapshot contains 18 unique recorded payment offers associated only with Bolivia: 9 classified as collections and 9 as payouts. All 18 have a BOB association. These are offer records, not independent PSPs, live integrations or approved routes. Separate country, currency and method associations do not verify every combination.
PayStar Discovery structures research and qualification around your company, business activity, volumes and separate collection and payout requirements. Include your branch and account structure in that brief. The merchant selects and contracts directly with the PSP; the PSP processes payments and provides settlement under that agreement.
Want information about these payment options for free? Just write to us.
Contact Anastasia by email or Telegram. Free information concerns these payment options. Availability and eligibility require confirmation; integration, processing and other Discovery work are scoped separately.