> 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/appendix/enumeration/response-code-list.md). # Response Code List

No	HTTP Code	SVC Code	RC Code	RC Desc
1	200	00	00	Success
2	200	20	01	Invalid Field Format
3	200	20	02	Process not allowed
4	200	20	03	Invalid Customer Token
5	200	20	04	Customer Not Found
6	200	20	05	Card Not Valid
7	200	20	06	Transaction Not Found
8	200	20	07	Acq not found
9	400	10	00	Bad Request
10	400	10	01	Invalid Field Format {field name}
11	400	10	02	Invalid Mandatory Field {field name}
12	401	10	00	Unauthorized. [reason]
13	401	10	01	Invalid Token (B2B)
14	401	10	02	Invalid Customer Token
15	401	10	03	Token Not Found (B2B)
16	401	10	04	Customer Token Not Found
17	403	10	00	Transaction Expired
18	403	10	01	Feature Not Allowed [Reason]
19	403	10	02	Exceeds Transaction Amount Limit
20	403	10	03	Suspected Fraud
21	403	10	04	Activity Count Limit Exceeded
22	403	10	05	Do Not Honor
23	403	10	06	Feature Not Allowed At This Time. [reason]
24	403	10	07	Card Blocked
25	403	10	08	Card Expired
26	403	10	09	Dormant Account
27	403	10	10	Need To Set Token Limit
28	403	10	11	OTP Blocked
29	403	10	12	OTP Lifetime Expired
30	403	10	13	OTP Sent To Cardholer
31	403	10	14	Insufficient Funds
32	403	10	15	Transaction Not Permitted.[reason]
33	403	10	16	Suspend Transaction
34	403	10	17	Token Limit Exceeded
35	403	10	18	Inactive Card/Account/Customer
36	403	10	19	Merchant Blacklisted
37	403	10	20	Merchant Limit Exceed
38	403	10	21	Set Limit Not Allowed
39	403	10	22	Token Limit Invalid
40	403	10	23	Account Limit Exceed
41	202	10	00	Request In Progress
42	404	10	00	Invalid Transaction Status
43	404	10	01	Transaction Not Found
44	404	10	02	Invalid Routing
45	404	10	03	Bank Not Supported By Switch
46	404	10	04	Transaction Cancelled
47	404	10	05	Merchant Is Not Registered For Card Registration Services
48	404	10	06	Need To Request OTP
49	404	10	07	Journey Not Found
50	404	10	08	Invalid Merchant
51	404	10	09	No Issuer
52	404	10	10	Invalid API Transition
53	404	10	11	Invalid Card/Account/Customer [info]/Virtual Account
54	404	10	12	Invalid Bill/Virtual Account [Reason]
55	404	10	13	Invalid Amount
56	404	10	14	Paid Bill
57	404	10	15	Invalid OTP
58	404	10	16	Partner Not Found
59	404	10	17	Invalid Terminal
60	404	10	18	Inconsistent Request
61	404	10	19	Invalid Bill/Virtual Account
62	405	10	00	Requested Function Is Not Supported
63	405	10	01	Requested Opearation Is Not Allowed
64	409	10	00	Conflict
65	409	10	01	Duplicate partnerReferenceNo
66	500	10	00	General Error
67	500	10	01	Internal Server Error
68	500	10	02	External Server Error
69	504	10	00	Timeout
70	429	10	00	Too Many Requests
71	200	20	08	Rule not allowed
72	200	21	01	Initiation Error
73	200	21	02	Create Session Error
74	200	21	03	Update Session Error
75	200	21	04	Authentication Error
76	200	20	09	3DS tanpa interaksi
77	200	20	10	Rule not allowed
78	200	21	05	Check Auth Error
79	200	21	06	Authorize Error
80	200	22	01	Fraud
81	200	21	07	Capture Error
82	200	21	08	Void Error
83	200	21	09	Refund Error
84	200	21	10	Payment Error
85	200	20	11	Reject by Rule
86	409	10	02	Duplicate data

--- # 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/appendix/enumeration/response-code-list.md?ask=&goal= ``` `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.