Integration After KYB Approval

✅ Post-KYB Integration Flow

Once KYB is approved, the client proceeds to:

Select a provider
Choose the service(s) to activate (e.g. QR Code Payment, Virtual Account)
Submit the required API credentials (Client Key, Client Secret)
Click Test Connection & Save

This action triggers an automated connection test, during which Paystrator also sends the required callback URL to the provider.

🔄 What Happens During Connection Test

When the client submits the form, Paystrator will:

Generate a short-lived Bearer token using the provided credentials
Detect whether the environment is sandbox or production
Send a POST request to the provider’s registered test endpoint for that environment
Include in the payload a standardized callback endpoint that must be stored by the provider

📤 Payload Sent to Provider

{
  "service": "qrcode",
  "env": "sandbox",
  "endpoint": "https://sandbox.paystrator.com/v1/callback/receive/qrcode/{codename}"
}

Field Descriptions

Field	Description
`service`	The service being activated (e.g. `qrcode`, `virtual_account`, etc.)
`env`	The environment in which the connection test is performed
`endpoint`	The callback URL Paystrator expects the provider to use for notifications

{codename} is automatically generated by Paystrator and uniquely represents the provider-service combination.

📡 Paystrator Callback URL Format

Paystrator uses a standardized format for all callback endpoints:

Sandbox

Receive Money:
https://sandbox.paystrator.com/v1/callback/receive/{type}/{codename}

Send Money:
https://sandbox.paystrator.com/v1/callback/send/{type}/{codename}

Production

Receive Money:
https://api.paystrator.com/v1/callback/receive/{type}/{codename}

Send Money:
https://api.paystrator.com/v1/callback/send/{type}/{codename}

Supported `type` Values

Receive Money: qrcode, virtual_account, ewallet, credit_cardreceive
Send Money: bifast, reguler

🧾 Request Headers

Content-Type: application/json
Authorization: Bearer <generated_token>

✅ Expected Provider Response

The provider must respond with the following structure:

{
  "status": "passed"
}

Field	Description
`status`	Must return `"passed"` if the connection test was successful (in both sandbox or production)

If the response is not "passed", the provider will not added as new provider.

Yellow = Sandbox Passed
This indicates the provider’s API has passed testing in the sandbox environment only. The service is not yet live, further testing is required in production.
Green = Production Passed
This means the provider’s API has successfully passed all integration diagnostics in the production environment. The service is fully available for clients to use in live transactions.

Our Goal:
We encourage providers to ensure all services turn green, so clients can immediately begin using them without delays or manual steps..

🛠️ Provider Responsibilities

To support this automated flow, the provider must:

Expose test endpoints for both sandbox and production
Validate the Bearer token in the request header
Parse the service, env, and endpoint fields from the request body
Store the provided endpoint internally for future callback delivery
Respond with { "status": "passed" } if all validations succeed

📋 Integration Checklist

Requirement	Status
Provide sandbox and production test endpoints	✅
Accept and validate Bearer token	✅
Parse and store Paystrator’s callback `endpoint`	✅
Return `{ "status": "passed" }` on success	✅
Use the stored `endpoint` for actual callbacks	✅

🤝 Need Help?

If you need assistance in preparing your sandbox and production endpoints, please contact your integration manager.