> For the complete documentation index, see [llms.txt](https://prepaidify.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prepaidify.gitbook.io/docs/virtual-card/page-integration/login-free-page-integration.md).

# Login-free Page Integration

## Brief Description

* Integration of login-free page, API interface integration required, users exempted from email verification.
* This integration method requires customizing your own domain for access. Ach can perform mapping. Please provide your domain name and the corresponding SSL certificate. Contact technical support for configuration.

## Environment Information

`Unmapped URLs:`

* Test Environment Domain: <https://sbx-card-api.prepaidify.com>
* Production Environment Domain: <https://card-api.prepaidify.com>

`Mapped URLs:`

* Test Environment Domain: https\://{merchant-defined-url}
* Production Environment Domain: https\://{merchant-defined-url}

## Request Path

* /open/merchant/api/v2

## Request Method

* POST
* Content-Type: application/json

## Request Parameter

| Parameter | Sign | Mandatory | Type   | Length | Desc           |
| --------- | ---- | --------- | ------ | ------ | -------------- |
| email     | Y    | N         | string | 64     | Email address  |
| appId     | Y    | Y         | string | 32     | Merchant appid |
| sign      | Y    | Y         | string | 512    | Signature      |

### Request Example

JSON

```json
{
  "email": "123@qq.com",
  "appId": "qmamnbodyqzbdr0w",
  "sign": "8979EEB59CF15246A04E033962CA4084973A9D0F2F5CC08F07B99E9D0338F4486ED7700CF78F6365C2E399ED593B3EF9059F2EC808B5107CED8CC17BA0475962"
}

```

## Response Parameter

| Parameter | Type    | Desc                                                     |
| --------- | ------- | -------------------------------------------------------- |
| code      | string  | Please refer to the code description for coding details. |
| msg       | string  | Response message                                         |
| model     | object  | Returned when successful                                 |
| traceId   | string  | -                                                        |
| success   | boolean | Status of successs                                       |
| error     | boolean | Status of fail                                           |

### Response Example

Successful Response Example

JSON

```json
{
  "code": "0",
  "msg": "成功",
  "model": {
    "webUrl": "To use the test environment, contact us to enable permissions"
  },
  "traceId": "64461f5414909b4b1e05a58fd7e818d1",
  "error": false,
  "success": true
}

```

Failed Response Example

JSON

```json
{
  "code": "1006",
  "msg": "Signature error",
  "model": null,
  "traceId": "644622ad97df9eed485ae837c9a48d5a",
  "error": true,
  "success": false
}

```

> For more information on return codes, please refer to the code description.


---

# 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, and the optional `goal` query parameter:

```
GET https://prepaidify.gitbook.io/docs/virtual-card/page-integration/login-free-page-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.