Merchant acceptance pilot · instant-payment rails today

A lower-friction way to accept public digital money.

CivicPay is building the merchant acceptance layer for modern public money: QR checkout, payment status, receipts, refunds, reconciliation, and integration-ready records—starting with supported instant-payment rails.

CivicPay is not a bank, does not issue digital currency, and does not currently offer CBDC acceptance. Future CBDC compatibility depends on program rules, approved access, and partner arrangements.

Merchant console

Pilot flow preview

Supported rail

Checkout

Ready to present

Payment status

Confirmation recorded

Receipt record

Order CP-1048

Reconciliation

Daily review ready

Illustrative interface concept. Availability and timing vary by payment rail and partner setup.

Designed for merchant operations

Accept at the moment of sale.

01 / Acceptance

Replace fragmented payment handoffs with a clear request your customer can scan, open, and complete through an eligible payment method.

QR checkout. Present a scannable payment request in store or at the counter.

Checkout links. Send a branded link for remote, invoice, or marketplace flows.

Payment status. Give staff a clear status signal when a supported payment is confirmed.

Keep proof close to the payment.

Surface clear payment status and issue receipts that staff and customers can reference.

Make exceptions less manual.

Bring refunds and end-of-day reconciliation into the same workflow rather than stitching records together later.

How it works

A clear flow, from request to reconciliation.

  1. 01

    Create a payment request

    Choose a QR code, checkout link, or connected point-of-sale flow.

  2. 02

    Receive a clear status

    Use the payment update and receipt record to keep the sale moving.

  3. 03

    Close the books

    Review refunds, daily reconciliation, and exports from one operating view.

Pilot economics

A transparent acceptance model built for lower-cost rails.

Pilot pricing, eligible payment methods, and service scope will be shared with selected merchants. The intended model is a small transaction fee with optional software and integration services.

Built for a practical launch path

Start with merchant operations on available instant-payment rails. CBDC readiness is future positioning—not a claim of current availability or approval.

For teams that need integration readiness

Keep transaction records ready for accounting exports, marketplace workflows, and future developer API connections.

Merchant pilot

Help shape the acceptance layer merchants actually need.

Tell us where you accept payments today. We'll share pilot details as rails, partners, and merchant eligibility are confirmed.

Read our approach

By requesting access, you agree to hear from CivicPay about the merchant pilot. No payment details are collected here.