How does an Abitab payment work?
The shopper picks Abitab at checkout. The provider creates the payment and returns a voucher or payment instructions, which the shopper can print or keep on a phone. The payment is pending at this point. The shopper visits an Abitab branch, pays the amount in cash, and Abitab passes the collection to the provider, which marks the payment as paid so the merchant can release the order.
The timing is slower than a card. dLocal lists Abitab with a maximum voucher expiry of seven days, a minimum amount of 15 UYU and a notification delay of one to three working days after the shopper pays. Mercado Pago, which offers Abitab in Uruguay through Checkout Pro and its Checkout API, returns a link with payment instructions and keeps the payment pending until the buyer pays. Its documentation says cash payments must be made within three to five business days, and payments that are not completed are cancelled or expire. Bamboo Payment returns a coupon link with a validity date and lets the merchant set the expiry.
dLocal supports a direct flow, where the merchant shows the voucher on its own page, and a redirect flow to a provider-hosted page.
Why does Abitab matter for merchants?
Uruguayan e-commerce is card-led. A May 2026 report by CEDU and Exante, published by Montevideo Portal, found that credit cards paid for 68% of online spending, with debit and e-money making up the rest. A cash option reaches the shoppers that leaves out, such as people without a credit card, people who prefer not to enter card details online, or customers whose card has been declined. Offering Abitab next to cards gives them a way to complete the purchase.
The network is large. Citi Uruguay’s collections guide describes more than 500 Abitab branches across the country, and dLocal calls Abitab one of the largest collection networks in Uruguay. Bamboo Payment says its collection points take cash for e-commerce purchases as well as service payments. Major providers in the country, including Mercado Pago and dLocal, offer it alongside Redpagos, the other national network, so a merchant can cover both with one provider.
A paid voucher is final for the merchant. The shopper paid in cash at a branch, so no card chargeback can pull the money back.
What can go wrong?
Vouchers go unpaid. A share of shoppers never visit a branch, and their orders stay pending until the voucher expires. A seven-day window gives shoppers time but holds stock for a week.
Confirmation lags. At dLocal the notification can take one to three working days after the shopper pays, so Abitab is a poor fit for orders that must be fulfilled the same day.
Orders can ship unpaid. A merchant that relies on the browser redirect instead of the provider’s paid status can release goods that were never paid for.
Refunds need a separate route. dLocal lists refunds as supported for Abitab, but the shopper paid in cash, so the provider has to return the money another way. Confirm the process before launch.
How would Omno handle Abitab?
Abitab would be offered in the hosted checkout as a cash option, or offered through Direct Links for merchants with their own checkout. The voucher would be shown to the shopper, the payment would stay pending, and the paid or expired status would arrive by webhook, which is the source of truth for fulfilment. The merchant could set the expiry per order within the provider’s limit. Merchant rules could show Abitab only for UYU orders above the provider’s minimum, and routing rules would choose among providers that support it. In the hosted checkout, if the chosen provider were unavailable or rejected the request, the payment would move to the next provider in the rule until one accepts. The routing-decision log would record which provider handled each payment.