Amounts typed by hand
Static QRIS leaves the total to the customer. A per-order checkout presents the exact amount instead.
Early-access pilot · Built for independent merchantsYour QRIS.
Your QRIS.
Connected to every order.
Sell online or in person with the QRIS you already use. Create a checkout for each order, match incoming payments, and update your store—without changing your payment destination.
Pay per verified transaction · Connector availability confirmed during onboarding
THE PAYMENT PATHILLUSTRATIVE FLOW
01
An order is created
Your storefront, POS, or sales link requests a new invoice.
02
The customer scans
Show a QRIS checkout linked to the order and its exact total.
03
Payment is matched
An enabled merchant connector supplies the incoming payment signal.
04
Your business moves forward
Verified status reaches your system through a webhook or dashboard.
order → payment → statusone transaction, one outcome01 / The problemPayments arrive.
Payments arrive.
Order status stays behind.
A QR code accepts money. It doesn't, by itself, tell your shop which order was paid. That gap slows down every sales channel.
Payments checked one by one
Match incoming merchant-side payment data to open orders, with ambiguous matches held for review.
Sales channels stay disconnected
Give a website, sales link, or POS the same payment status through an API and webhook.
02 / One layer, multiple storefrontsBuilt around the way
Built around the way
you already sell.
Whether customers meet you at a counter or on a screen, every paid order needs a dependable status.
One payment link for every order.
Send a checkout from a website, a social conversation, a service invoice, or a point-of-sale screen. Your system keeps the order reference.
Your exact total
Merchant name, reference and payment status appear together.QR PREVIEW
NOT PAYABLE
NOT PAYABLE
MERCHANT-FIRST
Your existing QRIS stays yours.
We work on the order and payment-information layer. The customer pays the connected merchant QRIS; Axvila Pay is not the destination for that payment.
↗
Connected, not replacedSource compatibility is checked for each merchant account during the pilot.
WEB STORESALES LINKSIN-PERSONPOSAPI
One payment event → your existing workflow
03 / Pricing model
Pay for payments you can actually reconcile.
Usage-based pricing, measured per verified transaction. No monthly seat fee is part of the proposed model. The pilot rate and billing terms are shared before onboarding.
PROPOSED BILLING UNIT
Per verified transaction.
One matched payment that moves one order to paid counts once. Repeated notifications and webhook retries do not create extra billable events.
- No charge on an unmatched notification
- No charge on an unpaid or expired order
- Pilot rate disclosed before activation
Before you connect.
Can I use the QRIS I already have?
That's the intended starting point. The QRIS format and the merchant-side payment signal both need to pass a compatibility check. A QR image alone cannot report that money arrived.
Does this work without an Android device?
It depends on the merchant connector. An authorised provider transaction feed can run without a device; a notification-based connector needs a merchant-side Android device running. Device-free support is not universal.
Where does my customer's money go?
The checkout uses the connected merchant's QRIS. Axvila Pay is designed as a payment-information layer, not the account that receives the customer's QRIS payment. The merchant's existing settlement arrangement remains with its QRIS provider.
Does every payment automatically mark an order paid?
No. Only a payment that can be matched to the correct merchant and order with adequate evidence should change status. Late, duplicate, unmatched, or ambiguous signals belong in a review queue.
Is the API open for production use?
The product is in an early-access pilot. Production access, supported merchant connectors and the per-transaction rate are confirmed individually before activation.
EARLY ACCESSKeep the QRIS.
Request pilot access Keep the QRIS.
Connect the sale.
Tell us where you sell and which merchant QRIS you use. We'll check the integration path and pilot fit.