Set up online payments
Tenant Admins use Settings → Online payments to configure PayHere checkout. Payment requests and online checkout have separate availability states.
Before you start
- Your tenant must have online payments enabled and your role must allow configuration.
- Have the PayHere merchant credentials for the intended environment ready.
- Confirm with PayHere that your merchant account accepts your application’s domain.
- Use the Test checkout card for sandbox credentials and the Live checkout card for live credentials.
Do not paste credentials into support messages or ordinary notes.
Save and enable
- Open the intended Test checkout or Live checkout card.
- Save both merchant credential values. These fields are write-only and clear after submission.
- Review the displayed configuration checks. They cover credentials, credential setup, the allowed checkout address, the payment notification address and the customer return address.
- Resolve missing configuration. Ask support for help with notification or return addresses.
- Choose Enable test checkout or Enable live checkout for the current credentials.
- Run an authorized test payment and check its saved result before offering live payment to customers.
The configuration checks do not contact PayHere or prove that notification delivery works. Enabling checkout does not run a payment, approve a privacy review or prove merchant acceptance.
Expected result
The card shows checkout enabled for that environment and credential version. A payable request can offer a secure handoff when the server’s permissions, amount, currency and current request state also allow it.
PayHere handles payment entry. Motornauts confirms payment from a validated provider callback and its saved records. Browser return alone is not proof of payment success.
Change credentials or stop checkout
Saving new credentials turns checkout off for the changed configuration. Check the new setup and explicitly enable it again. Existing payment attempts keep the configuration context needed to verify their callbacks.
Use Turn off checkout to stop new checkout for the selected environment. This does not convert pending payments into failed payments or erase their history.
Common problems
| What you see | What to do |
|---|---|
| Enable button is unavailable | Resolve the card’s missing configuration checks. |
| Checkout turned off after a save | Recheck the new credentials and enable that environment again. |
| PayHere rejects the handoff | Verify merchant/domain acceptance with PayHere; local checks cannot prove it. |
| Payment result stays pending | Follow payment troubleshooting; do not submit another payment just to refresh status. |
| Review reminder remains | Keep provider/privacy reviews assigned to their owner. Review reminders do not automatically disable an enabled feature. |
Read customer approval and payment for the customer journey, or module readiness for other availability states.