Midtrans

Connect Midtrans to PayLexer to accept cards, bank transfers, e-wallets, and local Indonesian payment methods.

Midtrans is an Indonesia-focused payment gateway supporting a wide range of local and international payment methods including credit and debit cards, bank transfers, e-wallets (GoPay, OVO, Dana, ShopeePay), QRIS, and convenience store payments. It operates primarily in Indonesia and supports both one-time and recurring payments through its Snap and Core API products.

Supported Regions (Merchant Accounts): Indonesia
Supported Currencies: IDR (Indonesian Rupiah); international card payments may be accepted depending on your merchant account configuration

Supported Features

Credit and debit card payments (Visa, Mastercard, JCB, American Express)
Bank transfers (BCA, BNI, BRI, Mandiri, Permata, and others)
E-wallet payments (GoPay, OVO, Dana, ShopeePay, LinkAja)
QRIS (Quick Response Code Indonesian Standard)
Convenience store payments (Indomaret, Alfamart)
3D Secure (3DS) card authentication
Sandbox and production environments
Webhook notifications for real-time payment status updates

Before You Start

Make sure you have:

Midtrans Account – Don't have one? Sign up for Midtrans →
PayLexer Account – Required to configure the integration. Create your account →
A website where you want to integrate

Looking for a different payment processor? View all supported gateways →

Configuring Midtrans

You need a Server Key and Client Key from Midtrans for this integration. Separate credentials are required for Sandbox and Production environments.

Getting API Credentials

Go to the Midtrans production dashboard or the Midtrans sandbox dashboard and sign in.

Open Access Keys

In the left sidebar, click Settings, then select Access Keys.

Midtrans Settings menu with Access Keys highlighted

Copy your Server Key and Client Key

You will see two keys on this page:

Server Key - used by PayLexer for server-side API calls. Keep this secret.
Client Key - used for client-side payment forms.

Copy both keys. Repeat these steps in the other environment (sandbox and production) so you have both sets of credentials.

Midtrans Access Keys page showing Server Key and Client Key fields

Your Server Key is sensitive. Never expose it in client-side code, public repositories, or logs.

Adding Credentials to PayLexer

Open PayLexer Dashboard

PayLexer Payment Gateways page with Midtrans option

Enter your credentials

Paste the Server Keys and Client Keys you copied from Midtrans:

Server Key (Live) - paste your production Server Key
Client Key (Live) - paste your production Client Key
Server Key (Test) - paste your sandbox Server Key
Client Key (Test) - paste your sandbox Client Key

PayLexer Midtrans credential fields for Server Key and Client Key

Understanding Live/Production and Sandbox Settings:

Environment	Purpose
Live / Production (Mandatory)	Used for real transactions. Cannot be empty, even when testing.
Test / Sandbox (Optional)	Used for testing only. No real money is processed.

How PayLexer selects credentials:

Debug/Test mode ON → Test credentials are used
Debug/Test mode OFF → Live credentials are used

Save your configuration

Click Save Configuration to store your Midtrans credentials in PayLexer.

Your Midtrans credentials are saved and ready to use.

Configuring Webhooks (Mandatory)

Webhooks enable real-time payment updates and significantly improve reliability. Midtrans calls webhooks "HTTP Notifications" in the dashboard.

Benefits of Webhooks:

Instant payment status updates for cards and e-wallets
Real-time settlement notifications for bank transfers, which can complete hours after initiation
Automatic handling of payment method callbacks (GoPay, OVO, QRIS, and others)

Copy your PayLexer webhook URL

In your PayLexer dashboard, go to Payment Gateways → Midtrans and copy the Webhook URL shown on the page.

This URL is generated by PayLexer for your account - copy it exactly as displayed, without editing it.

Open Notification settings in Midtrans

In your Midtrans dashboard, go to Settings → Configuration.

Midtrans Settings menu with Configuration option

Set the Payment Notification URL

In the Payment Notification URL field, paste the PayLexer webhook URL you copied.

Optionally set the Finish Redirect URL and Unfinish Redirect URL to your checkout result pages.

Midtrans Configuration page showing Payment Notification URL field

Save the configuration

Click Update to save the notification URL.

Midtrans will now send payment status notifications to PayLexer automatically.

Save your Server Key as the Webhook Secret

Midtrans signs notifications using your Server Key. PayLexer uses this to verify that incoming webhook events are genuine.

In your PayLexer dashboard, go to Payment Gateways → Midtrans and paste your Midtrans Server Key into the Webhook Secret field, then click Save Configuration.

Integrate Midtrans to Your Website

If you have already added and configured your site, you can enable Midtrans in your existing setup.

Go to Websites

Navigate to Websites in your PayLexer dashboard.

PayLexer Websites page showing added websites

Edit your website

Click the Edit Icon of your added website.

Enable Midtrans

Click the checkbox to enable Midtrans for the website.

You can enable multiple gateways on a single website and let customers choose at checkout.

If you haven't added a website yet, Continue to Add Your Website →

Troubleshooting

Confirm you copied the correct key type - Server Key starts with SB-Mid-server- (sandbox) or Mid-server- (production).
Make sure you are not mixing sandbox keys with the Live fields or production keys with the Test fields.
Check that there are no extra spaces before or after the keys when pasting.
Regenerate your keys in the Midtrans dashboard under Settings → Access Keys if you suspect they are compromised.

Verify the Payment Notification URL in Midtrans Settings → Configuration exactly matches the PayLexer webhook URL.
Confirm your PayLexer webhook URL is publicly accessible (not a localhost address).
Check that the Webhook Secret in PayLexer matches your Midtrans Server Key.
Use the Midtrans dashboard notification log to see if delivery attempts are failing and review any error responses.

Check that webhooks are configured correctly - without them, PayLexer relies on the redirect callback which can be skipped if the customer closes the browser.
In the Midtrans dashboard under Transactions, confirm the payment status is Settlement or Capture.
If the status is Pending, the payment method (for example, bank transfer) may not have been completed by the customer yet.
Ensure Test Mode in PayLexer matches the environment (sandbox vs. production) you used for the transaction.

E-wallet and QRIS availability depends on your Midtrans account activation. Check Settings → Payment Methods in your Midtrans dashboard to confirm which methods are enabled for your merchant account.
Some payment methods require separate activation by Midtrans. Contact Midtrans support if a method is missing.

Best Practices

Always test with sandbox credentials before going live to confirm the full payment flow works end-to-end.
Configure webhooks - they are the most reliable way to receive payment status updates, especially for bank transfers and e-wallets that may complete minutes or hours after initiation.
Store only the minimum data you need from payment responses; never log or store your Server Key.
Use distinct sandbox and production Midtrans accounts when possible to avoid accidental live charges during testing.
Monitor the Midtrans transaction dashboard alongside PayLexer to cross-reference payment statuses during initial rollout.

FAQs

Live credentials are mandatory to save the configuration. Test credentials are optional but highly recommended so you can safely test payments before going live.

Check the Debug Mode setting in your platform. When Debug Mode is ON, PayLexer uses your Test credentials. When OFF, it uses Live credentials.

Transactions appear in three places: your platform's booking or order pages, PayLexer Dashboard → Orders, and Midtrans Dashboard. All three show the same transactions with different IDs.

Payments will still process, but status updates may be delayed. Check webhook logs in Midtrans Dashboard to troubleshoot.

Midtrans primarily operates in Indonesia and processes transactions in Indonesian Rupiah (IDR). Some international card payments may be accepted depending on your merchant account configuration. Contact Midtrans directly for details on multi-currency or cross-border support.

No. A single Midtrans merchant account provides both a sandbox environment and a production environment. Each environment has its own set of Server Key and Client Key, which you enter into the respective Test and Live fields in PayLexer.

The Server Key is used for secure, server-side API calls (creating payment intents, verifying webhooks). It must never be exposed publicly. The Client Key is used in client-side payment forms (such as Snap.js) and is safe to use in frontend code.

Bank transfers in Indonesia require the customer to manually complete the transfer through their bank app or ATM. The payment remains Pending until the customer completes the transfer. This can take up to 24 hours. Midtrans will send a webhook notification to PayLexer once the payment settles.

Midtrans supports card tokenization which can be used to charge customers repeatedly. PayLexer's subscription support for Midtrans depends on your plan. Check the Supported Payment Gateways page for the latest feature availability.

Still Have Questions?

Midtrans Support: Midtrans Help Center
PayLexer Support: Contact Support

For full API reference and advanced configuration, see the Midtrans developer documentation.

Was this page helpful?

Last updated today

Built with Documentation.AI