Skip to content

SATUSEHAT and BPJS integrations

Connecting the clinic's payment gateway account (QRIS and Virtual Account)

Updated 2 Nov 2026

In this article

The clinic accepts patient QRIS and Virtual Account (VA) payments through its own payment gateway merchant account, so the funds go straight to the clinic's account.

What you need

  1. A payment gateway merchant account in the clinic's name (KYB documents are handled directly with the payment gateway provider). The supported provider is named on the payment gateway card under Integrations → Credentials; the Medivana team can help if you are unsure.
  2. From the payment gateway dashboard: the API Key, Client ID, Client Secret, and the Account ID of the account that receives the funds.
  3. The Medivana server IP registered in the payment gateway dashboard's IP whitelist menu (ask the Medivana team for the IP address).

Steps

  1. Open Integrations → Credentials, pick the payment gateway card (VA, QRIS, payment link), and choose Set up.
  2. Fill in the API Key, Client ID, Client Secret, and Account ID. Choose the sandbox environment for testing or production for real transactions.
  3. Optional: restrict the Enabled methods (e.g. qris,va_bri,va_mandiri), choose the Checkout mode (native shows the QR/VA number directly in Medivana; payment_link opens the payment gateway's payment page), and fill in the Settlement receiving COA account if settlements go to an account other than 1111 Operating Bank.
  4. Save, then press Test connection. A successful result lists the payment methods enabled on the merchant account.
  5. Copy the Transaction notification URL shown on the payment gateway card and register it in the payment gateway dashboard as the transaction, product expiration, and settlement notification URL.

Secrets (API Key, Client Secret) are stored encrypted and never shown again; leave the field empty if you do not want to change it.

Common problems

Symptom / message Cause What to do
Test connection: credentials rejected Wrong API Key, Client ID, or Client Secret, or sandbox/production mixed up Copy them again from the payment gateway dashboard for the right environment
"The Medivana server IP is not registered" / access denied The IP is not whitelisted Add the Medivana server IP in the payment gateway dashboard
Test connection: Account ID not found The Account ID does not belong to that merchant Check the account ULID in the payment gateway dashboard
Paid in the payment gateway dashboard but unchanged in Medivana The notification URL is not registered Register the notification URL; meanwhile Medivana checks the status automatically every few minutes

Baca dalam Bahasa Indonesia