> 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/appendix/json-object/additional-info-object.md). # Additional Info Object | No | Name | Type | Mandatory | Min Length | Max Length | Description | | -- | ------------------ | ---------------------------------------------------- | --------- | ---------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | tips\_indikator | String | O | 2 | 2 | 00 no tips 01 tips 02 percentage tips | | 2 | tips\_fixamount | String | O | 16,2 | 16,2 | Required, if tips\_indikator = 01 | | 3 | tips\_percentage | String | O | 16,2 | 16,2 | Required, if tips\_indikator = 02 | | 4 | note | String | O | 1 | 50 | Transaction remark | | 5 | qr\_type | String | M | 2 | 2 | 11 static 12 dynamic | | 6 | callback\_payment | String | O | 1 | 100 | URL Notify Payment | | 7 | merchantId | String | O | 1 | 64 | Merchant identifier, unique per each merchant | | 8 | subMerchantId | String | O | 1 | 32 | Sub Merchant ID | | 9 | nmid | String | O | 1 | 12 | National Merchant ID, required when Payment Notify Request | | 10 | validityPeriod | String | O | 1 | 25 | The time when the QRIS invalid | | 11 | cust\_name | String | M | 1 | 25 | Buyer Name | | 12 | merchantName | String | M | 1 | 25 | Merchant Name | | 13 | rrn | String | M | 1 | 12 | Unique Transaction | | 14 | nns\_issuer | String | M | 1 | 8 | Issuer Institution Number, Ex. 93600777 | | 15 | nns\_acquirer | String | M | 1 | 8 | Acquirer Institution Number, Ex. 93600777 | | 16 | mpan | String | M | 1 | 20 | Merchant PAN | | 17 | cpan | String | M | 1 | 20 | Customer PAN | | 18 | sof\_id | String | M | 1 | 19 | Ex. “qr\_statis”, “qrdinamis” | | 19 | invoice | String | M | 1 | 64 | Invoice number from partner | | 20 | issuer | String | O | 1 | 25 | Name of Issuer PSP | | 21 | acquirer | String | O | 1 | 25 | Name of Acquirer PSP | | 22 | FeeAmount | [Object](/appendix/json-object/fee-amount-object.md) | O | 1 | 2 | Detail Of Fee Amount | | 23 | paidTime | String | O | 1 | 25 | The time when the QRIS paid | | 24 | phoneNo | String | O | 1 | 16 | Customer phone number to be inquired (Required for Finpay Money Linkage) | | 25 | accountStatus | String | O | N/A | N/A | Customer account status (Required for Finpay Money Linkage) | | 26 | otp | String | O | 1 | 16 | OTP from SMS sent to customer phone number. (Required for Finpay Money Linkage) | | 27 | clientId | String | O | N/A | N/A | Filled with OAuth client id from X-PARTNER-ID (For Finpay Money Linkage) | | 28 | redirectToDeeplink | String | O | N/A | N/A | Last redirection target after successfully verifying the PIN, value is obtained from the redirect field on oauth\_clients table. (For Finpay Money Linkage) | | 29 | transationDesc | String | O | 1 | 256 | Transaction description (Required for Finpay Money Linkage) | | 30 | transactionType | String | O | 1 | 32 | Transation type (Required for Finpay Money Linkage) | | 31 | partnerReferenceNo | String | O | 1 | 32 | Transaction identifier on service consumer system (For Finpay Money Linkage) | | 32 | referenceNo | String | O | 1 | 32 | Transaction identifier/reference generated by PJP AIS Selain Bank. (For Finpay Money Linkage) | | 33 | trxCode | String | O | N/A | N/A | (For Finpay Money Linkage) | | 34 | id | String | O | N/A | N/A | (For Finpay Money Linkage) | | 35 | sum\_in | String | O | N/A | N/A | (For Finpay Money Linkage) | | 36 | sum\_out | String | O | N/A | N/A | (For Finpay Money Linkage) | | 37 | channel\_id | String | O | N/A | N/A | (For Finpay Money Linkage) | | 38 | source | String | O | N/A | N/A | (For Finpay Money Linkage) | | 39 | destination | String | O | N/A | N/A | (For Finpay Money Linkage) | | 40 | name | String | O | N/A | N/A | (For Finpay Money Linkage) | ``` { "additionalInfo":{ "cust_name": "CANDRA GUNAWAN GAHO", "merchantName": "BB011 WARTEG MUSTIKA", "rrn": "000019001390", "nns_issuer": "93600014", "nns_acquirer": "93600777", "mpan": "9360077732302230011", "cpan": "9360001410190013903", "nmid": "ID1023249949984", "sof_id": "qr_statis", "issuer": "BCA", "acquirer": "Finpay", "note": "Transaction Remark", "merchantId":"FM1234567700", "paidTime":"2024-06-07T10:03:54+07:00" } } ``` --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.finpay.id/appendix/json-object/additional-info-object.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.