Creating Sample Requests

Remember that PaymentsOS provides a single API for transacting against multiple providers. When constructing a request body, you must thus ensure that you include all fields required by the providers to which a payment may be routed. This may seem like a daunting task, but do not despair! You’re about to shake hands with our Bodybuilder, the only heavyweight champion in the world capable of lifting JSON!

Meet our Bodybuilder

It may take you some time to determine what fields you must include in your transaction requests. So why not let our Bodybuilder do all the heavy lifting for you? Simply use the form below to build a POST request body with just a few clicks of the mouse. Over time, our Bodybuilder will gain more muscle and additional request types and providers will appear in the list.

Select request type

Select providers





































Optional and 3DS Fields

To include 3DS fields, first select optional fields and then select a provider. Showing fields for a specific 3DS flow is disabled if that flow is not supported by either the provider or the selected request type.




Risk Fields

To include PayU Risk fields, first select a provider. The option is disabled if PayU Risk is not supported by either the provider or the selected request type.


Sample header will be displayed here

Output will de displayed here.
Last modified December 7, 2021