A business collecting XOF from customers and paying a field team has two deadlines: the customer must be able to pay, and the recipients must receive their money on time. A successful checkout alone does not establish when those collections become available to fund the next payout batch.
We reviewed 8 historical country-only payment-offer records for Burkina Faso: 4 collections and 4 payouts, from a gateway-supplied snapshot dated 14 September 2026. They provide a starting point for a commercial conversation, not a count of methods, independent providers or active connections. This guide explains how to compare collection costs, settlement instructions and the outcome of each individual payout.
1. What the eight records can tell you
The eight unique records are associated with XOF and only Burkina Faso in the supplied country links. Wider multi-country offers are excluded from this count. A currency or payment-method association does not prove that every possible combination is operational or available to your company.
Four records in each direction are too small a private commercial cohort for this article to publish representative fees, ranges or settlement distributions. We therefore withhold those details. There is also no consistent transaction-level conversion sample with a shared denominator and observation window: no observed conversion average is available.
The original commercial statements were supplied by gateways and have not been independently verified. Terms may change weekly or more often. The arithmetic below uses explicitly invented assumptions, not those private tariffs.
2. Merchant acceptance, online collection and group payment are different products
Burkina Faso's local Orange Business pages make a useful distinction. Merchant payment requires a contract and a merchant account/code. Its separate online-payment page describes an NDA, test API integration, a contract and an agreed frequency for compensations. Its group-payment page requires a contract and accounts for the recipients. Those are separate scopes to confirm with the provider. Merchant payment, online payment, group payment.
For a merchant, the practical question is whether the contract covers the operation you need: counter payment, website collection, a recipient batch, or a combination. Confirm whether collected funds can finance payouts directly, must first be settled elsewhere, or require a separate funded account. We do not assume that prefunding is mandatory for every provider or that Orange's products share a balance.
Orange's own Burkina Faso shop describes an OTP obtained through a USSD flow. That is evidence of that shop's customer journey, not a universal specification for all integrations. Test your approved journey on the intended handsets, including expiry, cancellation and lost connectivity. Do not treat a customer's screenshot as final merchant-side confirmation. Orange shop payment help.
3. On a small ticket, the fixed fee can change the result
Invented example — not an Orange tariff, a quotation or a market average. Suppose tariff A charges 1.8% + XOF 50 for a successful collection, while tariff B charges 2.4% with no fixed component. Both examples exclude taxes, refunds, settlement charges, FX and other costs.
At XOF 2,500, A costs XOF 95 and B costs XOF 60. At XOF 15,000, A costs XOF 320 and B costs XOF 360. The lower percentage loses on the smaller ticket and wins on the larger one. Compare each offer against your own ticket distribution; neither invented tariff is universally cheaper.
Obtain written answers about minimum fees, charges on failed attempts, reversals, account funding and bank transfers. If a payout recipient later withdraws cash, check who pays that separate charge and how it is disclosed. A transfer amount, a recipient's wallet credit and the cash ultimately withdrawn are different amounts unless the tariff proves otherwise.
4. Fund a batch using available money, not expected collections
Invented cash-flow example — no actual provider timing or prefunding rule is implied. A business plans 20 payouts of XOF 7,500, totalling XOF 150,000. It has XOF 120,000 usable in the account assigned to this batch. Another XOF 50,000 of collections is pending and cannot yet be used under the example's assumptions. The funding gap is XOF 30,000, before payout fees. Pending collections do not close it merely because they appear in a dashboard.
After the business supplies the missing XOF 30,000, assume 18 rows succeed, one fails and one remains pending. That means XOF 135,000 confirmed, XOF 7,500 failed and XOF 7,500 unresolved. These are invented outcomes, not a 90% performance claim. The status labels do not establish whether money for the failed or pending row is still reserved, debited or already returned; reconcile those movements separately.
The operating decision is concrete: when must the batch account be funded, which balance is usable, and when can unresolved funds be released or safely retried? Agree the funding currency, value date, cut-off, weekend treatment, reserve policy and evidence of final credit. A recorded T+0 label, if offered, would describe a term to clarify, not measured receipt by every beneficiary.
5. A batch receipt is not the outcome of every row
Ask the provider for a sample batch report before signing. It should let your team connect the business instruction, batch reference, immutable row reference, beneficiary, amount, currency, provider transaction reference, status and financial movement. Preserve the original provider reason alongside any simplified internal status.
Use a repeatable acceptance test: send an approved test batch with a valid recipient, an invalid recipient and a deliberately interrupted request. Establish which response means accepted for processing and which establishes success. Confirm how to query an uncertain row and how repeated submissions are detected. A timeout is not permission to send the same payout again with a new reference.
Set an owner and a deadline for unresolved rows. Reconciliation should explain opening balance, funding, settled collections where applicable, payouts, fees, holds, returned amounts and closing balance. These are recommended operating controls; the official product pages do not by themselves confirm that any particular API or report supplies them.
6. Check the provider's scope and your business eligibility
BCEAO publishes a register of payment institutions under its payment-services framework. The retrieved release is dated 28 February 2026 and is one category of regulated institutions, not a list of every bank, electronic-money issuer or possible payment route. Use the appropriate current register and the provider's legal identity to verify the exact service scope before onboarding. BCEAO payment-institution register.
Orange Burkina's B2B page asks for an established legal structure, a contract and documents covering registration, the responsible person's identity and address. This is a provider-specific starting list, not a general approval for a non-resident business or every industry. Confirm your activity, ownership, customer geography, recipient type and settlement destination. Any cross-border or restricted-business proposal needs its own applicable legal and compliance review. Local B2B requirements.
PI-SPI is an additional regional infrastructure to discuss where relevant. BCEAO states that access depends on the customer's institution being connected. Its existence does not show that a shortlisted provider exposes your desired batch operation or that a business receives free processing. Verify the actual account, service and tariff separately. BCEAO PI-SPI.
7. PayStar's role
PayStar provides information and agreed technical services. PayStar is not a bank or payment service provider, does not arrange payment acceptance or settlement in its own name, does not receive or hold customer or merchant funds, and does not settle them. The merchant chooses the PSP and signs a direct agreement with it. The selected provider delivers the payment services, processing and settlement under that agreement.
PayStar Discovery can help structure the shortlist and the commercial questions. Where separately agreed, PayStar Direct Connect supplies a technical API layer and PayStar Core supports routing, monitoring and reconciliation within PayStar's agreed technical role. These services do not guarantee eligibility, provider availability, conversion or settlement outcomes.
8. Ask for a collection-and-payout brief
For Burkina Faso, request a comparison that includes your typical ticket, monthly XOF collection volume, payout batch size, recipient type and the time by which usable funds are needed. Ask for collection and payout fees separately, the account funding path, per-row reporting, refund rules, limits and required business documents.
Anastasia can provide information about payment options free of charge. This refers to the information, not free processing, integration or all Discovery services. Current availability and eligibility need separate confirmation with the selected provider.
Contact Anastasia on Telegram or by email: Anastasia@PayStar.uk.
9. Sources and data boundaries
Commercial snapshot: 14 September 2026. Official product and regulatory sources were reviewed 2 October 2026. The eight records are historical gateway statements, not a market census, a count of PSPs or a promise that an integration is live. We counted distinct offers and excluded multi-country records. Private provider identities, contacts and individual commercial terms are not reproduced. Public operator names above identify published product documentation; they do not identify the suppliers behind the private records.
The fee and batch diagrams are explicitly fictional teaching examples. No actual tariff, settlement distribution or conversion rate is claimed. Official pages can change; reconfirm terms and applicable authorisations before a release or onboarding. Cover scenes are editorial AI illustrations inspired by Bobo-Dioulasso's earthen architecture, not verified documentary views. Architectural context: UNESCO tentative-list entry for Sya.