NeoPay

Applications and API access

Prepare a NeoPay application and its access while preserving separate Test/Live modes and IP restrictions.

Prepare the application

In the merchant space’s Applications and API section, check which application, mode and access to use. Payment account activation and application mode are separate settings. Keep existing access unchanged unless a change has been agreed.

Server authentication

The API receives an application token in Authorization: Bearer and the same application’s identifier in x-app-key. Keep both values on your server; do not put them in public JavaScript, a URL or a message intended for the customer.

Authorization: Bearer YOUR_APPLICATION_TOKEN
x-app-key: YOUR_APPLICATION_ID
Accept: application/json

Allowed IP addresses

The public outbound IP of the server calling NeoPay must match an IP allowed for the application. It may differ from the visitor’s address or the address displayed for the domain. A header added by the browser does not replace this check.

First read-only check

Using the Test application’s access, a GET request to /api/links checks authentication and access to its links without creating a link or triggering payment. A 401 response indicates an authentication issue; a 403 response can concern the account or an allowed IP.

GET https://neopay.io/api/links