> For the complete documentation index, see [llms.txt](https://v2.docs.securepay.my/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.docs.securepay.my/basics/interfaces.md).

# Interfaces

The **Interface (API)** page allows merchants and developers to manage system integration settings, including API credentials, virtual account configuration, settlement rules,  redirect and callback URLs and connected payment gateways.

This page is primarily used by developers and technical teams to configure and maintain secure integration with SecurePay.

***

### Creating a New Interface

When creating a new interface, you will be asked to provide the following details:

#### General Settings

* **Name** – A unique name for your interface (e.g., `MyShop FPX`, `Wallet API`).
* **Status** – Active or Inactive. Only active interfaces can process payments.
* **Description** – Short description of the interface (optional).
* **Charge Mode** – Defines how charges are applied (e.g., *Merchant, Credit* or *Customer*).
* **Virtual account - Bank** – The account bank where settlement funds will be deposited.
* **Split Settlement** – Assign split settlement rule for the interface to split the fund to multiple accounts. 

***

#### URL Settings

These URLs determine how customers and your system handle the payment flow:

* **Redirect URL** – Where customers are redirected after a successful payment.
* **Cancel URL** – Where customers are redirected if they cancel the transaction.
* **Callback URL** – Your system’s endpoint for receiving server-to-server notifications about payment results.
* **Timeout URL** – Used when the transaction session expires before completion.

***

#### Gateway Settings

You can enable different payment channels under an interface.

**FPX**

* **Gateway** – Choose the FPX bank gateway (e.g., *Hong Leong Bank UAT*).
* **Charge Mode** – Defines how charges are applied (e.g., *Merchant, Credit, Customer* or *Inherit*).
* **Bank View** – How banks are displayed to customers.
* **Bank Type** – Choose between **B2C (Retail customers)** or **B2B (Corporate customers)**.

**DuitNow**

* **Gateway** – Select the DuitNow participating bank.
* **Charge Mode** – Defines how charges are applied (e.g., *Merchant, Credit, Customer* or *Inherit*).
* **Bank View** – How banks are shown (*List*).
* **Bank Type** – Typically **Retail**.

***

### Example Workflow

1. **Create Interface** – Define general settings, URLs, and enable required payment gateways.
2. **Use Interface in Forms** – Assign an interface for the payment form.
3. **Redirect Customer** – After payment, the customer is redirected to the configured URL.
4. **Receive Callback** – Your system processes transaction results via the callback URL.
5. **Settlement** – Funds are deposited into the chosen account bank or based on the split settlement rules that is assigned to the interface.

<figure><img src="/files/7xlruTjlO2RSJpQIZajL" alt=""><figcaption></figcaption></figure>


---

# 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://v2.docs.securepay.my/basics/interfaces.md?ask=<question>
```

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.