Use Cases
From infrastructure to commerce: how each vertical operates on Impala.
Retail, Travel and Services are the highest-volume verticals on the E-Commerce Gateway, the Hospitality Gateway and the Recurring Payments Gateway.
Retail
E-Commerce Gateway
01
New stores live in days, not months
Who it's for
Retail chains and D2C brands launching or migrating their store on Shopify, VTEX, WooCommerce, Wix or BigCommerce.
Pain point
Every new store or country demands a custom payments integration, with weeks of development before the first sale.
How Impala solves it
Native pre-integration: checkout is ready from the platform plugin, with no custom development.
Measurable result
-80%
time-to-market for new merchants
02
Capture mobile volume without extra friction
Who it's for
Retailers whose traffic is already mostly mobile (social channels, marketplaces, apps).
Pain point
Traditional card checkout loses sales against the digital wallets and local alternative payment methods customers already use.
How Impala solves it
No-code enablement of digital wallets and local APMs (alternative payment methods) on the same gateway.
Measurable result
1 in 3
mobile conversions recovered at checkout
Travel
Hospitality Gateway
01
The end of mass declines on OTA virtual cards
Who it's for
Hotels and vacation rentals receiving bookings from Booking.com, Expedia and other OTAs (online travel agencies).
Pain point
OTA VCCs (virtual credit cards) are declined on standard terminals, leaving bookings without confirmed payment.
How Impala solves it
A virtual terminal specifically authorized to process VCCs from the main OTAs.
Measurable result
Confirmed collection
in the OTA channel, with no VCC declines
02
Tokenized security deposits and fewer no-shows
Who it's for
Vacation rentals and boutique hotels that depend on the security deposit.
Pain point
Collecting the deposit by hand — or not at all — exposes the merchant to no-shows and disputes.
How Impala solves it
Payment links, QR codes and tokenized deposit management, chargeable before check-in.
Measurable result
-90%
impact from no-shows and uncollectable stays
Services
Recurring Payments Gateway
01
Expired cards no longer break the subscription
Who it's for
Memberships, subscription software and monthly plans with a recurring cardholder base.
Pain point
Expired or reissued cards break automatic collection and trigger involuntary cancellations.
How Impala solves it
Card Account Updater (CAU) connected in real time to Visa and Mastercard, plus network tokens, keeping credentials always current.
Measurable result
+30%
recovery of recurring revenue
02
Bulk collection integrated with the core, ERP or operating system
Who it's for
Schools, clinics, insurers or companies with bulk billing integrated into internal systems.
Pain point
Recurring collection lives apart from the system managing students, patients or policies, duplicating data and reconciliation.
How Impala solves it
Credential-on-File API for bulk collection, integrable with banking cores, ERPs, CRMs and education or healthcare systems.
Measurable result
One system
for customer relationship and recurring collection
Glossary
The language of payments, without ambiguity.
Industry acronyms hide business decisions. Here they are translated into the impact they have on your operation.
FAQ
Frequently asked questions
What is the difference between an Impala product and a use case?
The product is the transactional engine (E-Commerce Gateway, Hospitality Gateway, Recurring Payments Gateway, Orchestrator). The use case describes how a real Retail, Travel or Services merchant operates that engine day to day.
Which verticals do the use cases cover?
Retail and D2C on the E-Commerce Gateway, Travel and hospitality on the Hospitality Gateway, and Services with recurring billing on the Recurring Payments Gateway.
Can one merchant combine several use cases?
Yes. The engines share integration, tokenization and reporting, so a group can run retail, stays and subscriptions on the same infrastructure.
Do these use cases apply across Latin America?
Yes. Each case runs with dynamic routing by country, issuer and acquirer, so the same operation can be replicated across markets in the region.