Skip to content
Back to home

API payments

Make payments part of your product.

Connect payments to orders in your website or application. Compare two approaches: a ready checkout page or your own payment form.

Integration that fits

Shape your customer’s payment journey.

Create the order in your own system and start the payment using the appropriate approach. Receive the result, match it to the order and follow its record in your panel.

Hosted API

Send customers to a ready checkout page.

Use the generated payment address when you prefer a prepared checkout page. Your customer completes the required payment steps there.

  • A ready payment surface
  • Payments linked to orders
  • Results for your system
Product experience
Transactions matched to orders
Connect the payment record to your own order. Let your system track which payment belongs to each sale.
Receive and verify results
Verify results through transaction notifications and status queries. A customer’s browser return screen alone is not proof of payment.
A separate test environment
Try the integration in sandbox before going live. Manage test and live access details separately in your panel.
Connect account operations
Add supported account operations when needed, including reading balances and requesting refunds or withdrawals through your integration.

Choose the approach

A ready page or your own form?

Hosted and Direct offer different customer experiences. Consider page development, your application’s structure and the payment steps you need to support before choosing.

  • Start with a ready page
  • Build your own form
  • Handle required redirections
Open developer guide
Product experience

Connect the outcome

Keep payment and order status aligned.

Starting a payment is the first part of the process. Verify incoming results, monitor pending transactions and update the order according to the confirmed payment outcome.

  • Verified transaction results
  • Tracking pending states
  • Records in your panel
Open developer guide

Prepare

Test the flow before using it live.

Prepare test access in your panel and work through the developer guide’s examples. Complete the access requirements that apply to your account before live use.

  • Try the sandbox
  • Follow the developer guide
  • Meet account access requirements
Open developer guide
Product experience

API payments

Three integration stages

  1. Choose an approach

    Select Hosted or Direct to fit the payment experience in your product.

  2. Build a test flow

    Try payment creation, result handling and status checks in sandbox.

  3. Follow live use

    Once access requirements are met, track live transactions alongside your panel.

Complete your existing product

An e-commerce website

Connect payments while keeping your own product and order infrastructure.

Orders from an application

Match the payment result to orders started in your application.

Online services

Track payment status as you manage the next stage of a service sale.

Your questions

Does Direct always keep the customer on the same page?

No. A transaction may require verification or a provider redirect. Your integration must handle the required steps and verify the payment result afterwards.

Where are the integration instructions?

The developer centre has separate guides for Hosted, Direct and account operations. Request examples, results and test steps are explained there for your technical team.

Does test access include live access?

Sandbox and live access are managed separately. Obtaining live keys and processing transactions depend on your account permissions and completion of the required test steps.

Build the right payment flow for your product.

Choose an approach, prepare test access in your panel and work through the developer guide with your technical team.

Create account

Product access, limits and fees depend on the conditions of your account.