Skip to main content
FastFlowPe sends real-time PayIn transaction status updates to a webhook endpoint of your choosing. Whenever a PayIn transaction reaches a terminal state, FastFlowPe automatically POSTs a JSON payload to your pre-configured HTTPS URL, so your system stays in sync without polling.
Quick ReferenceProtocol: HTTPS only (HTTP endpoints are rejected)Method: POST with JSON bodyEvent: PayIn transaction status changeSetup path: Merchant Dashboard, Settings, Webhooks, Credit - PayIn, UpdateActivation: 2 to 3 minutes after saving

​
How to Configure Your PayIn Callback URL

Register your PayIn webhook URL in the merchant dashboard before FastFlowPe can deliver PayIn callbacks to your server.
1

Log in to the merchant dashboard

Navigate to https://go.fastflowpe.com/ and sign in with your merchant credentials.
2

Open Webhook Settings

From the left sidebar, click Settings, then select the Webhooks tab.
3

Enter your PayIn callback URL

Under Credit - PayIn, enter your HTTPS endpoint URL where you want FastFlowPe to deliver PayIn transaction callbacks.
4

Save the configuration

Click Update under Credit - PayIn to save your URL. Full path: Login → Settings → Webhooks → Credit - PayIn → Update.
Only HTTPS-enabled webhook URLs are accepted. HTTP endpoints will be rejected and will not receive any callbacks.
Allow 2 to 3 minutes after saving your callback URL for the configuration to take effect. The next PayIn event after that window will be delivered to your endpoint.

​
PayIn Callback Payload

FastFlowPe uses a POST request with a JSON body for all PayIn callbacks.
PayIn Callback

​
PayIn Payload Fields

​
string
The unique UUID of the PayIn transaction.
​
string
The order ID you submitted when creating the PayIn transaction.
​
string
The transaction amount as a decimal string.
​
string
The payment mode used (e.g., QR, UPI).
​
string
The Unique Transaction Reference issued by the bank. null on failure.
​
string
The final transaction status. Either SUCCESS or FAILED.
​
object
An object containing customer information associated with the transaction.
​
string
The parsed response message from the payment service provider.
In production, rely on callbacks rather than polling the PayIn Status endpoint. Webhooks reduce latency, cut down on unnecessary API calls, and ensure your system reacts to transaction outcomes in real time.
Configuring PayOut callbacks? See PayOut Callbacks.