> For the complete documentation index, see [llms.txt](https://docs.bizon.one/08.01/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bizon.one/08.01/api-payment-gateway/integration-reference.md).

# Integration Reference

## <mark style="color:blue;">General information and capabilities</mark>

Gateway's API is built in a REST style, based on the JSON-API specification. API provides universal programmatic access to operate through a payment page or directly in a host-to-host way.&#x20;

PCI-DSS Level 1 certified. We use the most advanced methods to protect your money, we have Strong Customer authentication, and 3D Secure for online card payments.

## <mark style="color:blue;">Features</mark>

* JSON-API based on RESTful JSON API standard
* Advanced authentication using client certificates
* 1-stage and 2-stage payments
* Payment flows: payment page or server-to-server using universal API
* 3-D Secure support
* Repeating payment without providing card number, expiration date, and cardholder name
* Optional fields for extra parameters
* Segment selection to divide payments
* Selection of the payment page language and layout
* Setting payment session expiration timeout
* Payments to the card (OCT)
* Passing of dynamic descriptor
* Recurrent payments
* Multicurrency
* Perform authorizations with zero-amount
* DSRP
* 3-D Secure 2.0 support

{% hint style="danger" %}
For security reasons, we use keys to Log In to Merchant dashboard
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bizon.one/08.01/api-payment-gateway/integration-reference.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
