Fix sandbox or endpoint-blocked gateway settings

PayerOne uses live payment credentials. Public PayerOne sandbox access is retired, and provider sandbox modes are disabled. A provider may have a test environment of its own, but enabling it in a PayerOne gateway makes that saved connection unavailable.

If you see Sandbox blocked

1. Open **Payment Gateways** and edit the affected connection.

2. Turn off **Sandbox Mode**. For Worldpay, turn off **Try Environment**.

3. Replace test credentials with credentials for your live provider account.

4. Save with **Update Gateway** and review a fresh checkout.

Do not send a real payment using test-account credentials.

If you see Endpoint blocked

Remove values from optional custom endpoint fields such as **Custom API Base URL**, **Custom Gateway Base URL**, **Custom Payment URL**, **Custom SDK Script URL**, and **Custom SDK CSS URL**. Leaving them blank uses the built-in provider integration. Arbitrary proxy URLs and alternate provider hosts are not supported.

For Antom-based Alipay or WeChat Pay, keep **API Base URL** blank for the default region unless your provider contract requires an approved regional host. Ask support to check that host if saving fails. Do not rewrite the URL to bypass the error.

A saved connection can still be blocked

The inventory can display an older saved configuration even when it cannot process a checkout or callback. Saving a label alone does not repair invalid credentials or a blocked endpoint. If the error remains, provide support with the provider name, gateway display name, and the exact error text. Keep keys, passwords, and signing secrets private.