Start with the order.
Generate a checkout with the exact total and your order reference, whether the sale begins online or at the counter.
ORDER → QRIS CHECKOUT
FOR MERCHANTS WITH THEIR OWN QRISGet paid on QRIS.
Get paid on QRIS.
Know which order.
One order, one exact amount, one clear payment status. Axvila Pay connects your existing merchant QRIS to a checkout, order matching, and your store's workflow.
Pilot availability is checked per merchant. Payment detection needs access to a supported merchant-side transaction signal; a QR image alone cannot report a payment.
Your QRIS remains yours.Pricing is per verified transaction, not a subscription.
axvila / payMERCHANT WORKSPACE
ORDER MATCHING · SAMPLE DATA
CONCEPT PREVIEWEvery payment has a place.
ORDER #AG-1042Online store
Rp 125.047MatchedORDER #AG-1041Counter sale
Rp 80.312ReviewORDER #AG-1040Payment link
Rp 95.016WaitingMatch merchant events to an order. Hold ambiguous ones for review.Open demo ↗
ONE PAYMENT LAYER FOR
Online storesPayment linksCounter salesService invoicesAPIs
01 / THE WORKFLOWFrom “someone paid”
From “someone paid”
to “this order is paid.”
The problem isn't accepting a scan. It's identifying what the scan paid for, and telling the right sales channel what happened.
Check the incoming payment.
A connected merchant-side source sends a transaction signal. Match it to the right order; send uncertain matches to review.
SIGNAL → MERCHANT → ORDER
Keep your business in sync.
Show the resulting status in your workspace. Once verified, notify your site or system with a webhook.
STATUS → YOUR SALES CHANNEL
02 / FITS YOUR BUSINESS
Keep your payment destination. Improve what happens after the scan.
Axvila Pay is designed as an order and payment-information layer. The connected merchant QRIS remains the destination for customer payment; merchant compatibility is tested during pilot onboarding.
- Already sellingWorks around your sales flow instead of making you move to a new storefront.
- Multiple channelsUse order references across a website, payment link, service invoice, or POS.
- Exceptions visibleLate, duplicated, or unclear events should be reviewable—not silently counted as a paid order.
- Integrate laterStart from a merchant workspace, then connect your own application through API and webhook flows as supported.
03 / PRICING MODELPay for the transaction.
Pay for the transaction.
Not another seat.
Axvila Pay is planned to charge per verified order payment. No flat monthly fee in the proposed model. Your pilot rate and billing terms are shared before activation.
WHAT COUNTS
One verified payment.One billable transaction.
- Unpaid or expired order: no transaction charge
- Duplicate event or webhook retry: no second charge
- Unmatched event: reviewed, not billed as paid
Good questions to ask.
Can I bring the QRIS I already use?
That's the starting point. We check your merchant QRIS and access to its transaction signal during onboarding. Owning a QR image alone isn't enough to detect payments.
Do I need an Android phone running?
That depends on the connector. A provider transaction feed may work without a device; notification-based detection needs the merchant's Android device online. Device-free support is not universal.
Does the customer pay Axvila?
No. The intended checkout uses the connected merchant's own QRIS. Axvila Pay is the order-status layer; the merchant's provider continues to handle receipt and settlement under its own arrangement.
When does an order become paid?
Not merely because a similar amount appears. A payment event must be associated with the correct merchant and order with adequate evidence. Unclear cases stay in review rather than triggering fulfilment.
Is the demo a real payment account?
No. It uses clearly labeled sample orders and local interactions to show the planned merchant workflow. It cannot accept QRIS payments or access a real merchant account.
EARLY ACCESS / MERCHANT PILOTKeep the QRIS.
Request pilot access Keep the QRIS.
Connect the sale.
Tell us where you sell and which merchant QRIS you have. We'll check whether there's a workable connection path.