SERVER 2 SERVER

Server-to-Server Payments

Create and control payment flows directly from your secure backend using FiatPe’s S2S APIs.

How Server-to-Server payments work

With a Server-to-Server integration, your backend creates the order, securely sends the payment details to FiatPe, and handles the action returned in the next array. Your server must confirm the final payment status before fulfilling the order.

Create a FiatPe order from your backend.
Initiate the payment using the required payment method and customer details.
Handle the Native, Redirect, or HTML Form action returned by FiatPe.
Verify the final result on your backend and process webhooks idempotently.

Supported response flows

Flow	Response action	How to handle it
Native	`otp_submit` and `resend_otp`	Collect the OTP in your interface and use the returned action endpoints to submit or resend it.
Redirect	`redirect`	Navigate the customer’s browser to the URL returned in `next[0].url`.
HTML Form	`html_form`	Render the returned `html_content` as a complete HTML document in the customer’s browser.

PCI DSS certificate is required

Server-to-Server access is enabled after compliance review.

To use FiatPe Server-to-Server payments, submit your valid PCI DSS certificate to FiatPe for verification. The feature remains disabled until the certificate and your integration setup are approved.

Your systems must protect payment credentials and sensitive customer data throughout collection, transmission, processing, and storage. Never log or store CVVs, card OTPs, full card numbers, API secrets, or other authentication data unless explicitly permitted by PCI DSS.

Available payment methods

Use the method-specific guides to implement and test each supported integration.

Payment method	Guide	Supported flows
UPI Collect	Open guide	Collect
UPI Intent	Open guide	Intent
Card	Open guide	Native, Redirect, HTML Form
Net Banking	Open guide	Redirect, HTML Form
Wallet	Open guide	Redirect, HTML Form