# Developer Tools

The Developer Tools section provides everything you need to integrate and test the SecurePay API effectively. Here you will find resources for authentication, sandbox testing, and debugging support.

### Environments

SecurePay provides two environments to support development and production use cases:

* **Sandbox Environment**
  * Designed for development and testing.
  * Safe for simulating transactions without processing real payments.
  * Provides test data, mock cards, and sample responses.
* **Production Environment**
  * Live environment for real transactions.
  * Requires a verified SecurePay account and approved supporting documents.
  * Transactions processed here are final and linked to actual settlement.

### Base URL

{% tabs %}
{% tab title="Production" %}
`https://console.securepay.my/api`
{% endtab %}

{% tab title="Staging" %}
`https://sandbox.securepay.dev/api`
{% endtab %}
{% endtabs %}

{% hint style="info" %}
When integrating, always begin in the **sandbox** to validate your workflows before moving to **production**. Partners will have different base URL.
{% endhint %}

### Available Tools

Within this section, you will find detailed guidance on:

* [Validate](https://v2.docs.securepay.my/basics/integrations/merchant/validate)
* [Get Banks List](https://v2.docs.securepay.my/basics/integrations/payments/bank-list)

Use these tools to streamline integration, ensure compliance with SecurePay standards, and speed up your go-live process.


---

# Agent Instructions: 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/integrations.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.