Introduction

Baiyar accepts QRIS, virtual account, e-wallet and retail payments. Create a payment link in the dashboard, or create payments from your server with the Merchant API.

	Sandbox	Live
Host	https://api.baiyar.com	https://api.baiyar.com
Key	bk_test_…	bk_live_…
Money	none: payments are simulated	real

Sandbox and live data are separate. Payments, links, balances and webhook endpoints from one environment do not appear in the other. Both share one host: the key you send decides which one you reach.

How a payment goes

1. Your server creates a payment with POST /v1/payments, including the amount and method.
2. Baiyar returns payment instructions, such as a QR code, virtual account number, wallet link or retail payment code.
3. The payer completes the payment through their bank or wallet.
4. Baiyar changes the status to paid and sends a payment.succeeded webhook. You can also read the latest status with GET /v1/payments/{id}.
5. After Baiyar matches the provider’s settlement evidence, the funds move from pending to available and Baiyar sends payment.settled.

The payment status moves from created to pending, then ends as paid, failed or expired. paid means the payer succeeded; settlement happens later.

The road

1. Create an account and keep it secure.
2. Create a project in the sandbox and get a test API key.
3. Make your first payment, share a payment link or send an invoice, and hear about payments with webhooks. Test payments shows how to try every outcome.
4. Verify your account and go live.
5. Follow your payments and balance, and look after your account in Settings.

The API reference describes each operation. Conventions covers rules shared by requests and responses.