Hosted payment page

What it is#

Your server requests a payment URL from the API, redirects the customer to that Tilopay page and receives the result on your callback URL.

Card data is typed on a Tilopay page: the merchant never sees a card number and the merchant server stays out of that flow.

The API operations for this path live in API · Hosted payment page.

Who it is for#

For teams that take payments with their own code but prefer not to build or maintain the card form. What you need is backend work: request the URL and handle the callback.

What you need before starting#

1. Your own credentials. There are no shared sandbox credentials: every developer gets theirs through developer registration.
2. API authentication. See authentication.
3. A callback URL of yours that can receive the transaction result.

How to confirm the state of a charge#

The result arriving on your callback is not the only signal available, and not every error response travels with an HTTP 4xx:

• Read how to read an error response before declaring success.
• Configure webhooks for the events you care about.
• If a call fails without a clear response, resolve the state with safe retries.

Environments#

Testing and production share the same host. See environments before taking real money.

Compliance#

Together with the no-code path, this is the one that exposes your infrastructure the least. Confirm the applicable scope with your compliance team.

If you prefer the form on your own site#

Use the JavaScript SDK: the design is yours and the data still does not pass through your server.