> For the complete documentation index, see [llms.txt](https://docs.finpay.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finpay.id/security/ip-whitelist.md).

# IP Whitelist

Restrict API access to trusted network addresses with IP whitelisting.

When IP whitelist is enabled, Finpay only accepts API requests from registered IP addresses that use your credentials. This reduces the risk of unauthorized API access.

{% hint style="info" %}
Use IP whitelist for production credentials. Review the list whenever your infrastructure changes.
{% endhint %}

### Before you enable IP whitelist

Make sure you have:

* A user account with permission to manage API credentials and IP whitelist
* The public IP addresses used by your server or gateway
* A rollback plan in case your network address changes

{% hint style="warning" %}
If you whitelist the wrong IP address, your API requests can fail until the list is corrected.
{% endhint %}

### Add an IP address to the whitelist

{% stepper %}
{% step %}

### Sign in

Sign in to the Finpay Dashboard.
{% endstep %}

{% step %}

### Open IP whitelist settings

Go to **Settings → IP Whitelist**.
{% endstep %}

{% step %}

### Add the address

Click **+ Add**.

Enter the public IP address you want to allow.
{% endstep %}

{% step %}

### Save the change

Click **Submit** to save the new whitelist entry.
{% endstep %}

{% step %}

### Verify API access

Send a test API request from the registered IP address.

Confirm the request is accepted.
{% endstep %}
{% endstepper %}

After the IP is registered, only listed IP addresses can send API requests with your Finpay credentials.

### When to update the whitelist

Update the whitelist when:

* You move your application to a new server or cloud environment
* Your internet provider changes your public IP address
* You add a new production or failover endpoint

Remove IP addresses that are no longer in use.

### Recommended security practices

* Whitelist only fixed and trusted public IP addresses.
* Keep production and non-production environments separate.
* Review the whitelist after infrastructure changes.
* Combine IP whitelist with [2FA Authentication](/security/2fa-authentication.md) for stronger account security.
* Control admin access with [User & Roles](/security/user-and-roles.md).

### Troubleshooting

If API requests fail after enabling IP whitelist:

* Confirm the request comes from a registered public IP address
* Check whether your server IP has changed
* Review the whitelist entry for typing errors
* Retry the request after saving the latest change

If the issue continues, review your current network path and update the whitelist with the correct public IP address.


---

# 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://docs.finpay.id/security/ip-whitelist.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.