Pix and cards in a Brazilian online store: confirming the payment
Compare payment methods through the full customer journey and operation: confirmation, costs, expiry, cancellation and reconciliation.
A customer selects Pix, copies the payment code and pays in their banking app. Back at the store, the order still says pending. Without a clear explanation, they may try to pay again or contact support. The problem lies between systems, even though payment itself succeeded.
For a store serving Brazil, offering Pix and cards means designing that handover. The team needs to know what the customer sees, what confirms receipt and how to investigate a mismatch. Adding two checkout icons is the easy part.
Map each payment journey
For Pix, display the amount, recipient information, a copyable code and the payment deadline where applicable. Someone shopping on a phone must be able to switch to their banking app and return to the order. A screen that only asks them to scan their own phone leaves that journey incomplete.
Brazil’s central bank describes Pix Cobrança as a payment request using a QR code or copy-and-paste code, payable immediately or on a due date.
For cards, show the total and the terms actually available. If instalments are offered, clarify their number and the corresponding total. A decline should allow another attempt without creating duplicate orders or unnecessarily deleting the information already entered.
Keep order creation separate from payment receipt
Store a reference linking the order and transaction. The confirmation page should communicate the known status; reaching a particular browser address must not, by itself, approve a payment.
Agree with the provider how the store will query transaction status and receive confirmation. Assign responsibility for exceptions. If payment arrived but the order remains pending, support needs a way to investigate without asking the customer to pay again as an experiment.
Compare the entire operating cost
Request current terms from the provider. Compare fees, settlement times, instalment conditions, refunds, support and reconciliation. Do not assume an advertised condition for a different account type applies to your business.
Test the reporting workflow. Can staff connect the amount charged, provider deductions and order? A lower fee may be less useful if every receipt requires manual investigation. The decision depends on volume and staffing, rather than a universal winner between payment methods.
Rehearse before opening the store
- Payment confirmed after the browser has closed.
- An expired payment request followed by another attempt.
- A declined card followed by another payment method.
- Cancellation before and after payment confirmation.
- A refund recorded and checked with the provider.
Run these scenarios in the provider’s test environment and record the results against the order. Before accepting real sales, check the account configuration and authorised validation process. The operation is ready when the store, provider and support team can explain the same transaction.
Continue with connecting inventory, shipping and payments.
About the author
Tiago F SantiagoComments
No comments yet
Share a question or an experience related to the article.
Related articles
