PayerURL setup and limits
Where: Admin → System → Payments → PayerURL
Before you start
Not integrated in this build: no PayerURL checkout and no callback handling, so nothing is granted through it. A manual crypto payment can never confirm itself, which is why it is never offered at checkout.
Step by step
- Open its Payments card and read the Not integrated/configuration-only notice.
- Store identifiers/credentials only if you need to retain that configuration.
- Do not advertise a working automated checkout through this card.
- If you accept money externally, verify it in the provider’s own account and use the supported manual plan/order process; do not treat a buyer return URL as proof.
Settings and behaviour
Not integrated in this build: no PayerURL checkout and no callback handling, so nothing is granted through it. A manual crypto payment can never confirm itself, which is why it is never offered at checkout.
| Field | Purpose |
|---|---|
| Merchant ID | Public identifier requested by this provider card. |
| Secret key | Private credential. May be supplied through the host environment; do not share it. |
| Webhook secret | Private credential. May be supplied through the host environment; do not share it. |
Check the result
For integrated providers use a sandbox transaction and verified confirmation. For non-integrated providers confirm the public site does not offer a nonfunctional checkout.
Common questions and troubleshooting
Credential not taking effect: host environment values override saved settings. Different vendor dashboard: use the provider link on the live screen; these instructions describe the forum controls, not a promise about an external dashboard’s current layout.