---
title: "WooCommerce with Plexo, CFE invoices and QR tickets, Uruguay"
description: "acuamania.uy case: WooCommerce ticket store with Plexo payments, CFE e-invoicing, BROU bank benefit by card BIN and QR check-in at the gate. 4,500+ orders."
url: https://lazarosantana.dev/en/cases/acuamania/
---

case 01 · ticket sales · Uruguay

# Online tickets for a water *park*

acuamania.uy sells its tickets on WooCommerce. Every purchase is charged through Plexo, gets its electronic invoice and reaches the customer as a QR ticket that is validated at the gate.

[View live site](https://acuamania.uy) [How it works](https://lazarosantana.dev/en/cases/acuamania/#recorrido)

*acuamania.uy*

Home page of acuamania.uy, the online ticket store of the Acuamanía water park in Uruguay

**4,500 *+*** paid orders

**16,000 *+*** tickets issued

valid ticket

Client

Acuamanía, water park in Uruguay

Team

Developer at DeepZide, alongside two other devs

My role

BROU benefit plugin, fixes to the e-invoicing plugin (built by another team), checkout, performance and Docker

Environments

Local, staging on Coolify and production on Docker

// the challenge

## One sale four systems

The park sells almost everything online and in season. A purchase does not end at payment: it has to go through the local gateway, the invoicing required by law and the park gate, **without the customer noticing any of it**.

If one piece fails, the problem shows up in the entrance queue, with the customer standing right there.

01

### Local payment

Uruguayan cards through Plexo, the gateway the country's banks use.

02

### Legally required invoice

Every paid order issues its electronic tax receipt. Every refund, its credit note.

03

### Benefits

Partner deals and BROU Recompensa, the Banco República benefit that depends on the card used to pay.

04

### Fast gate

One QR ticket per person, which staff validate in seconds from a phone.

// walkthrough of an order

## From cart to the gate

Five steps the customer experiences as one. Scroll down and watch them in order.

01 · cart

### Cart and partner deals

The checkout separates final consumers from companies, and validates the data each invoice requires. Partner deals are applied here. If the card is from BROU (the BIN says so, its first digits), the order enters BROU Recompensa without touching the prices.

BROU plugin · built checkout · improved

02 · payment

### Payment with Plexo

The local gateway charges the card. BROU Recompensa payments are routed to the BROU merchant and the rest to the general merchant, so each one settles separately.

BIN routing · built Plexo · gateway

03 · invoice

### Electronic invoice

Once the payment is confirmed, an invoice plugin (built by another team) requests the tax receipt from Gsoft and stores it on the order, with its fiscal QR. A refund generates the credit note. Every attempt is kept in a log inside the admin, so a failure can be found without opening the server.

invoice plugin · by another team, fixed log · by another team

04 · ticket

### QR ticket

FooEvents issues one PDF ticket per person, each with its own QR, and the customer receives it by email along with the order.

FooEvents · third-party Brevo · third-party

05 · gate

### Gate control

Staff scan with the check-in app, which talks to the FooEvents API. A mu-plugin loads only what is essential on those calls, so validation does not wait for the rest of the site.

check-in mu-plugin · built FooEvents app · third-party

**cart** step 1 / 5

× 2

× 1

*4•••* •••• •••• ••••

checking BIN…

final consumer company · RUT

total · prices do not change **$ ••••**

**payment** step 2 / 5

**Store** order #•••••

**Plexo** local gateway

BIN of a BROU card? yes

→ BROU merchant

→ general merchant all other payments

routing diagram · no real data

**electronic invoice** step 3 / 5

e-ticket · CFE series • no. •••••

fiscal QR

wc · order paid

→ request to Gsoft

**✓ CFE issued · saved on the order**

if refunded → credit note

**tickets** step 4 / 5

3 attendees one PDF per person, by email

ticket 3 of 3

**gate** step 5 / 5

**scanning** check-in

ticket 1 of 3 **✓ check-in**

ticket 2 of 3 **✓ check-in**

ticket 3 of 3 …

illustrative · no real data

// real problems

## What breaks in production

Six cases taken from my commits on this project. Each card carries the commit that solved it.

`feat(acuamania-brou) · bfdfe8bc` built

### A coupon cannot be stacked with the bank benefit

If there is a coupon in the cart, BROU Recompensa is blocked. A second fix covers virtual coupons, which have no entry in the database.

`feat(acuamania-brou) · 6bbf816b` built

### New cards come with 8-digit BINs

The plugin accepts 6- and 8-digit BINs and compares the first 6, so no BROU card is left without the benefit.

`fix(efactura) · 7c4063ee` improved

### A mistyped digit left the order without an invoice

If the customer's document fails the check digit, the invoice is issued without it instead of failing. The recipient data goes in the XML that Gsoft accepts.

`feat(checkout) · 9fedfb40` improved

### Paying before filling in billing

The payment block stays closed until the billing details are complete, and the fields unlock in order.

`perf(fooevents) · 6ea4cadf` built

### The gate was waiting for all of WordPress

On the check-in app's REST calls only WooCommerce and FooEvents are loaded, and validation responds sooner.

`feat(emails) · be9c558d` improved

### An admin email for every abandoned payment

Orders that expire unpaid no longer notify as cancelled, and the inbox only receives what matters.

// under the hood

## What's behind the buy button

Where an order goes

customer**Browser** buys from a phone, with Turnstile against bots

park staff**Check-in app** validates the QR against the FooEvents API

administration**WordPress dashboard** orders, partner deals and the invoicing log

// server

### WordPress + WooCommerce

BROU benefit*BIN + routing**built*

mu-plugins*performance and check-in**built*

Electronic invoice (another team's plugin)*CFE and credit notes**fixed*

Child theme*checkout, partner deals, emails**improved*

Invoicing log*viewer in the admin**another team*

FooEvents*tickets and QR**third-party*

docker compose

Redis 7 · built PHP 8.2 · Apache · improved MariaDB 11.8 Traefik · Alloy · team

payments**Plexo** local gateway; BROU merchant and general merchant

invoicing**Gsoft** issues the tax receipt

email**Brevo** sends orders and tickets

New Improved Existing

// operations

## Fast in season safe when deploying

### From my machine to production

Every change goes through staging before reaching the live store. Production is updated by hand and always with a database backup first.

01**Local** working branch

02**Staging** Coolify · *develop* · automatic deploy

03**Production** *main* · backup and manual deploy

### Safeguards

**Less cart AJAX** the fragment calls WooCommerce makes on every page are trimmed

**Lightweight check-in** the app's calls load only the plugins they need

**XML-RPC closed** one less door for brute-force attacks

**Security headers** and PHP blocked in the uploads folder

**Redis and opcache** object cache and opcache sized above the site's file count

// result

## Store by the numbers

**4,500 *+*** paid orders

**16,000 *+*** tickets issued with QR

**4** external services connected: Plexo, Gsoft, Brevo and the check-in app

**3** environments: local, staging and production

WordPress WooCommerce PHP 8.2 FooEvents Plexo Gsoft · CFE Redis MariaDB Docker Coolify Cloudflare Turnstile Brevo

// next case

02 · corporate · Canada

### ratioweb.ca

Custom theme, bilingual, audited end to end: security, accessibility, performance and SEO.

*ratioweb.ca*

Home page of ratioweb.ca

[Need something like this? → WooCommerce stores for Uruguay](https://lazarosantana.dev/en/services/woocommerce-uruguay/)

[← all cases](https://lazarosantana.dev/en/#trabajo) case 1 of 4

// your project

## Want something like this for your business?

Tell me what you need. I reply within 24 hours and, if it is a fit, you get a fixed written proposal.

[Request a quote](https://lazarosantana.dev/en/contact/#form) [See services](https://lazarosantana.dev/en/services/)
