> For the complete documentation index, see [llms.txt](https://wallexpay.gitbook.io/api-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wallexpay.gitbook.io/api-doc/integration-guide/payment-terminal.md).
# Payment Terminal
Payment Terminal is a separate service which can help you to display your deposit address as a web page or embed it into your website as an i-frame.
As a merchant you need to generate a GET URL with a set of the established parameters according to the requirements below and redirect a user via that link to Payment Terminal. Data available for the user includes address and QR-code, currency and deposit amount (in case ‘amount’ parameter was sent).An example of implementation of Payment Terminal with i-frame
Once the user makes a deposit, it will be processed according to common deposit flow.
### Payment terminal workflow representation
## Creating a request
You need to create a request which contains hash with two required parameters: data and signature.
The request address:
** and signature'**
### **Data parameter generation**
You need to form JSON with [the following parameters](/api-doc/api-documentation/api-reference.md#payment-terminal-json-parameters)
**Example:**
```javascript
{
"client_id":1 ,
"url_back":"https:\/\/wallexpay.io\/?1588146480",
"amount":0.0005,
"foreign_id":"15881464801588146480",
"currency":"BTC",
"convert_to":"EUR"
}
```
You need to convert the resulting represented code in JSON to base64 format.
**Example:**
```
eyJhZGRpdGlvbmFsX3BhcmFtZXRlcnMiOnsiY2xpZW50X2lkIjoxfSwidXJsX2JhY2siOiJodHRwczpcL1wvY29pbnNwYWlkLmNvbVwvPzE1ODgxNDY0ODAiLCJhbW91bnQiOjAuMDAwNSwiZm9yZWlnbl9pZCI6IjE1ODgxNDY0ODAxNTg4MTQ2NDgwIiwiY3VycmVuY3kiOiJCVEMiLCJjb252ZXJ0X3RvIjoiRVVSIn0=
```
### **Signature parameter generation**
You need to:
* concatenate JSON with secret key to generate signature
**Example:**
```javascript
{
"pay_method":"method_x",
"user":"user1",
"amount":32.44,
"currency":"USD"
}
ObPvxgtazKCkQ7ifz3qzocbv9TVXeB1LUIbCsYk2WUt5agvyt1n1MhQnnCBlcwhY
```
* The calculated hmac(sha512) hash in lowercase looks like:
**Example:**
```
9e4c091dbcc9e2eca21e2e3bd6300ebec225dd0d80f4c309da9ace88000bf6da804262c1415a0b956d1d9411e05f55a547b234ce86338bc55ba58c9962ca0dad
```
As a result, the request will have the following look:
```
GET https://terminal.wallexpay.io/?data=eyJjbGllbnRfaWQiOjEsImN1cnJlbmN5IjoiQlRDIiwiZm9yZWlnbl9pZCI6MTU4OTI2ODI1N30=&signature=9e4c091dbcc9e2eca21e2e3bd6300ebec225dd0d80f4c309da9ace88000bf6da804262c1415a0b956d1d9411e05f55a547b234ce86338bc55ba58c9962ca0dad
```
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://wallexpay.gitbook.io/api-doc/integration-guide/payment-terminal.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.