# Payment Providers in Bolivia: QR Collections Across Branches

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.

## A numerical starting point for the provider comparison

We reviewed **18 unique historical payment offers** linked only to this country: 9 collection offers and 9 payout offers. They provide a structured starting point for comparing payment costs, access to funds and operational requirements. 64 additional offers linked to several countries are excluded from the country-only calculations below.

The source is the PayStar export dated 14 September 2026, supplied by payment gateways. We recomputed its aggregates, but did not independently verify its commercial statements. This is a historical sample, not a market survey, a count of PSPs or methods, or proof of active connections and current availability. Conditions can change weekly or more often. Independent country, currency and method associations do not establish every possible payment route. Direction counts and settlement-label charts cover all recorded currencies. Only the percentage comparison below is restricted to explicit BOB fee records.

18 unique offers linked only to this GEO, across all recorded currencies; not methods, providers or live connections. [Download SVG](https://paystar.uk/bolivia-payment-solutions/media/2026-10-08-v2/charts/offers-en-desktop-download.svg)

## What the recorded BOB percentage components show

We calculate the arithmetic mean of explicit percentage components stated in BOB, giving each comparable offer equal weight. A record qualifies only when its structured percentage matches one unambiguous percentage in the original fee description. Offers in another fee currency, missing percentages and ambiguous descriptions are excluded.

We also exclude bound or conditional percentages such as “from”, tiers and explicitly restricted customer categories. Exact nominal percentage components with fixed minimums or caps can remain in the sample; those minimums and caps still affect the final charge.

| Direction | n | Mean | Median | Range |
| --- | --- | --- | --- | --- |
| Collections | 9 | 6.34% | 6% | 5.5–9% |
| Payouts | 9 | 3.72% | 3% | 3–5.5% |

Explicit BOB percentage components only. n is the comparable sample in each direction; missing fees are excluded, not zero. [Download SVG](https://paystar.uk/bolivia-payment-solutions/media/2026-10-08-v2/charts/fees-en-desktop-download.svg)

**These are percentage components, not all-in payment prices.** Fixed charges, FX, tax, reserves, minimums and charges for refunds or other exceptions must be assessed separately. This sample is not weighted by payment volume, contains no measured conversion rate and cannot rank provider quality. Small or insufficiently independent groups are withheld.

### A hypothetical payment calculation

Take an illustrative payment of 100 BOB; this is not a typical market ticket. Applying the rounded means shown above gives:

- Collections: 100 BOB × 6.34% = **6.34 BOB**.
- Payouts: 100 BOB × 3.72% = **3.72 BOB**.

Each line is a separate direction, not a combined service quote. The arithmetic shows only the percentage part. Ask for an actual quote at your ticket size, volume, business model and settlement currency before calculating net proceeds.

## When money becomes usable matters

Collection offers across all recorded currencies. T/D labels are recorded as supplied, without assuming calendar or business days. Other includes complex labels and pooled groups below 3 records. No guaranteed settlement time. [Download SVG](https://paystar.uk/bolivia-payment-solutions/media/2026-10-08-v2/charts/timing-en-desktop-download.svg)

A successful payment notification and money available to your business are different events. Treat recorded settlement labels as questions for a provider: what starts the clock, which cut-off applies, are weekends counted, which account is credited, and can a reserve or review delay availability?

For payouts, agree prefunding, beneficiary validation, rejection handling and how returned funds appear in your balance. An incoming-payment settlement label does not prove payout completion time.

### A cash-buffer planning example

If a business must fund 10,000 BOB of obligations per day, a one-day gap requires 10,000 BOB; a three-day gap requires 30,000 BOB. The additional buffer is 20,000 BOB. This is a hypothetical constant-flow model, excluding fees, reserves and volatility, not an observed settlement promise.

## 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](https://www.bcb.gob.bo/webdocs/politicasbcb/IEF%20ene26%20%285%29.pdf).




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](https://www.bisa.com/empresas/bisa-QR).




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](https://apppro.bcp.com.bo/Multiplica/AuthIAM/Index).




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](https://apppro.bcp.com.bo/Multiplica/Inicio/TerminosCondiciones).




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](https://www.bisa.com/empresas/pago-a-proveedores).




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.

## The role of PayStar

PayStar provides information for comparing payment solutions and, where agreed, a technical layer for connecting and operating them. PayStar is not a bank or payment service provider and does not accept, hold or settle customer or business funds in its own name.

You select the payment provider and enter into a direct agreement with it. The provider processes payments and performs settlement under that agreement. Local eligibility, required authorisations and commercial terms must be confirmed for your company and use case. A method described in this article is not a promise that it is available through PayStar for your business.

Information about payment options is free. Payment processing and any agreed technical services have separate commercial terms.

## Official sources and research scope

- [Banco Central de Bolivia: Informe de Estabilidad Financiera, Enero 2026](https://www.bcb.gob.bo/webdocs/politicasbcb/IEF%20ene26%20%285%29.pdf)
- [Banco BISA: QR para empresas](https://www.bisa.com/empresas/bisa-QR)
- [BCP: Multiplica QR public entry page](https://apppro.bcp.com.bo/Multiplica/AuthIAM/Index)
- [BCP: Multiplica terms and conditions](https://apppro.bcp.com.bo/Multiplica/Inicio/TerminosCondiciones)
- [Banco BISA: Pago a Proveedores](https://www.bisa.com/empresas/pago-a-proveedores)

Research check: 8 October 2026. The export date remains 14 September 2026. Local scheme descriptions are context, not confirmation of a particular provider’s capabilities.