> 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/api-reference/finpay-money/linkage/reset-pin.md).

# Reset PIN

### E2E Flow <a href="#technical-specification" id="technical-specification"></a>

<figure><img src="/files/s8pCbUZSXPmLU0pa8Q8P" alt=""><figcaption></figcaption></figure>

### Technical Specification <a href="#technical-specification" id="technical-specification"></a>

| Environment | Method | URL                                                                                                |
| ----------- | ------ | -------------------------------------------------------------------------------------------------- |
| Development | POST   | [https://snapstag.finnet.co.id/v1.0/pin/reset](https://snapstag.finnet.co.id/v1.0/balance-inquiry) |
| Production  | POST   | [https://snap.finnet.co.id/v1.0/pin/reset](https://snap.finnet.co.id/v1.0/balance-inquiry)         |

### Body Request <a href="#body-request" id="body-request"></a>

| No | Name               | Type   | Mandatory | Min Length | Max Length | Description                                       |
| -- | ------------------ | ------ | --------- | ---------- | ---------- | ------------------------------------------------- |
| 1  | partnerReferenceNo | String | M         | 1          | 64         | Transaction identifier on service consumer system |
| 2  | phoneNo            | String | M         | 1          | 16         | Customer phone number with 08xx format            |

#### Sample Request <a href="#sample-request" id="sample-request"></a>

```
{
  "partnerReferenceNo": "789123434523423470",
  "phoneNo": "08113929190"
}
```

### Body Response <a href="#body-response" id="body-response"></a>

| No | Name            | Type                                                              | Mandatory | Min Length | Max Length | Description               |
| -- | --------------- | ----------------------------------------------------------------- | --------- | ---------- | ---------- | ------------------------- |
| 1  | responseCode    | [Enum](/api-reference/appendix/enumeration/response-code-list.md) | M         | 1          | 7          | BI SNAP Response Code.    |
| 2  | responseMessage | String                                                            | M         | 1          | 150        | BI SNAP Response Message. |

#### Sample Response <a href="#sample-response" id="sample-response"></a>

```
{
  "responseCode": "2000600",
  "responseMessage": "Request has been processed successfully"
}
```

### Response Code & Message <a href="#response-code--message" id="response-code--message"></a>

The table below lists results from `?verificationId=A0123AAS&result=success`.

| No | HTTP Code | Code    | Message                         |
| -- | --------- | ------- | ------------------------------- |
| 1  | 200       | 2000000 | Successful                      |
| 2  | 400       | 4000000 | Bad request                     |
| 3  | 400       | 4000001 | Invalid field format {field}    |
| 4  | 400       | 4000002 | Invalid mandatory field {field} |
| 5  | 401       | 4010001 | Invalid token (B2B)             |
| 6  | 401       | 4010000 | Unauthorised. \[Reason]         |
| 7  | 401       | 4010002 | Invalid Customer Token          |
| 8  | 401       | 4010003 | Token Not Found (B2B)           |
| 9  | 401       | 4010004 | Customer Token Not Found        |
| 10 | 403       | 4030001 | Feature not allowed             |
| 11 | 403       | 4030004 | Activity count limit exceeded   |
| 12 | 403       | 4030014 | Insufficient Funds              |
| 13 | 404       | 4040008 | Invalid merchant                |
| 14 | 500       | 5000000 | General error                   |
| 15 | 500       | 5000001 | Internal Server Error           |
| 16 | 500       | 5000002 | External Server Error           |
| 17 | 504       | 5040000 | Timeout                         |


---

# 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/api-reference/finpay-money/linkage/reset-pin.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.