Skip to main content
After submitting a payee registration via sp1401, you have two complementary ways to track the outcome. sp2402 is a synchronous polling endpoint — you can call it at any time to check the current status of a registration using either your merchant order number or Gcashier Pay’s internal flow reference. sp3401 is the asynchronous webhook: Gcashier Pay will POST the final review result — including the payeeId required for all future payment requests — directly to the callbackUrl you specified in sp1401. For most integrations, we recommend relying on sp3401 for automation and using sp2402 only for manual checks or reconciliation.

​
sp2402 — Payee Status Inquiry

​
Endpoint

POST https://{baseUrl}/api/sp2402

​
Request Parameters

​
merOrderNo
string
Your original merchant order number submitted in the sp1401 registration request. At least one of merOrderNo or bizFlowNo is required.
​
bizFlowNo
string
Gcashier Pay’s internal flow reference number returned in the sp1401 synchronous response. At least one of merOrderNo or bizFlowNo is required.

​
Request Example

{
  "merOrderNo": "318216608947200"
}

​
Response Body

​
mchOrderNo
string
required
Your original merchant order number for this payee registration.
​
bizFlowNo
string
required
Gcashier Pay’s internal flow reference number for this registration.
​
status
string
required
Current status of the payee registration. Possible values:
ValueDescription
01Under Review
03Rejected
04Normal (Approved)
05Deleted
​
payeeId
string
Conditionally returned when status is 04 (Approved). The unique payee identifier you will include in payment requests. Store this value securely.

​
Response Example

{
  "mchOrderNo": "318216608947200",
  "bizFlowNo": "64695022219410100019",
  "status": "04",
  "payeeId": "832b1bbaa5c04e5190342669438be566"
}

​
sp3401 — Payee Review Result Webhook

Gcashier Pay delivers an HTTP POST to your callbackUrl after every registration or modification review is completed. You do not need to initiate this call — the platform triggers it automatically.

​
Webhook Payload Fields

​
mchOrderNo
string
required
Your original merchant order number from the sp1401 submission, for correlation with your internal records.
​
bizFlowNo
string
required
Gcashier Pay’s internal flow reference number for the registration request.
​
status
string
required
The final review outcome. Possible values:
ValueDescription
04Approved — payee is active and ready to receive funds
03Rejected — see remark for the reason
​
remark
string
Conditionally included when status is 03 (Rejected). Contains the reviewer’s explanation of why the registration was declined. Use this information to correct and resubmit the payee via sp1401.
​
payeeId
string
Conditionally included when status is 04 (Approved). The unique identifier assigned to this beneficiary. You must supply this value in all subsequent payment orders targeting this payee.

​
Webhook Example

{
  "mchOrderNo": "318216608947200",
  "bizFlowNo": "323222444432",
  "status": "04",
  "remark": "",
  "payeeId": "832b1bbaa5c04e5190342669438be566"
}
Your webhook endpoint must return an HTTP 200 status code to acknowledge receipt. If Gcashier Pay does not receive a 200 response, it will retry delivery with exponential back-off. Implement idempotency on your end using the bizFlowNo to avoid processing the same notification more than once.