Skip to content

Customisable blueprint

Codex Pay

A customisable wallet and QR payments blueprint: balances, QR collect, payouts and an operations view of exceptions.

Overview

What this product is for

Codex Pay is a blueprint for a wallet and QR payment experience. Customers hold a balance, pay or get paid with a QR code, and support staff can see a payment that failed without reading a log file. The ledger rules, KYC tier and the scheme or acquirer behind the QR are chosen with the client. Codex Thrill does not operate a payment scheme.

Teams building a closed-loop wallet, a merchant QR collect flow, or a payout tool on top of a licensed payment partner.

At a glance

Customisable blueprint
Wallet and QR in one flow
Retries designed not to double-charge
Exceptions land in a queue, not a silent log

Capabilities

What is included

  • Wallet balance and transaction history
  • QR code to collect a stated amount
  • Payout request with a status the user can see
  • Idempotent payment commands so a retry does not double-charge
  • Exception queue for payments that need a person
  • Limits and step-up checks by KYC tier
  • Operations screen for refunds and manual adjustments, each with a reason

Stack

Technology

AngularNestJSPostgreSQLQR codesPayment partner API

Questions

Questions before a project conversation

Does Codex Pay hold customer funds?

No. Fund holding stays with the licensed institution or partner in the design. The blueprint is the software around that partner.

Which QR standard does it use?

The QR payload is chosen for the market and the acquirer. It is not locked to one national scheme in the blueprint.

Can a failed payment be retried safely?

Yes. Payment commands are designed to be idempotent, and a duplicate callback should not create a second debit.