Stop losing nights to ETA — your agent can issue every e-receipt in under 60 seconds

The 11pm problem

Every operator we talked to in Cairo told us the same story. The store closes, the orders pile up, and someone — usually the founder, sometimes a tired accountant — opens the ETA receipts portal at 11pm to issue receipts one by one. The portal is slow. The forms reject silently. The QR codes don't always attach. By 1am, half the receipts are still missing and tomorrow's fines are quietly accruing.

This is the single most-skipped task in Egyptian B2C accounting, and the cost of skipping it is real money.

A note on e-invoices: ETA's full e-invoice flow requires a USB signing device (HSM token) plugged into a physical machine. We don't automate that — it's a hardware-bound flow. **E-receipts**, which cover B2C sales, don't need the token and are what this workflow handles.

What the workflow actually does

The Wassel blueprint is one line of instruction to your agent:

On shopify.order.paid: issue the ETA Egypt e-receipt via Wafeq. Attach the QR code to the order. Send the customer their e-receipt via WhatsApp within 60 seconds.

Four integrations, zero glue code:

• Shopify fires the trigger the moment payment clears.
• Wafeq assembles the receipt with the correct VAT lines and seller details.
• ETA Egypt receipts API accepts and stamps it. The submission UUID comes back in the same call.
• WhatsApp Cloud delivers the QR receipt to the customer's phone.

Total wall time: under a minute, every time, with no human in the loop.

Why it matters

This isn't a productivity win. It's a risk-removal win.

1. No more 11pm portal runs. The agent doesn't sleep and doesn't forget.
2. Customers get their receipt while the purchase is still warm. That alone reduces "where's my receipt?" support tickets by 30 to 60 percent in the stores we've seen.
3. You stop being the bottleneck. New SKU? New tax rule? Edit the prompt. The workflow rebuilds itself.

Copy this into your own agent

The blueprint is on the Wassel template library. Open it, hit Use this template, and point your Claude, ChatGPT, or Cursor agent at the Wassel MCP endpoint. The first compliant e-receipt goes out before you've finished reading this paragraph.

If your stack uses a tool we don't list yet — different POS, different messaging channel — tell us. We're building the next integrations off the actual asks from operators, not a roadmap drawn on a whiteboard.