Order is the basic payment request for the standard integration with PayU.> If the response to the payment creation request is returned with an **HTTP 200** status and in HTML format, make sure that the tool used to communicate with PayU has automatic redirect handling disabled. Only in this case is it possible to receive the correct JSON response with an **HTTP 302** status code.
PayU Order API is one of 18 APIs that PayU publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
This API exposes 1 JSON Schema definition.
Tagged areas include Order. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 1 JSON Schema.
This API exposes
6 operations
across 5 paths,
and defines 46 schemas.
It is described by OpenAPI 3.1.0, at version 2.1.0.
Requests are made against 2 base URLs: https://secure.payu.com, https://secure.snd.payu.com.
6 operations5 paths46 schemas1 DELETE2 GET2 POST1 PUT
Metadata
The identity and technical contract details declared by the specification.
PayU Order API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (Bearer).
It accepts HTTP basic authentication (Basic).
By default, every request must be authenticated.
Paths & Operations 6
Across 5 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Order 6
Order is the basic payment request for the standard integration with PayU. If the response to the payment creation request is returned with an HTTP 200 status and in HTML format,…
The contract defines 46 schemas that model the data the API accepts and returns. The most detailed are accountInformation (17 properties), payMethod (12 properties), delivery (10 properties), buyer (9 properties). Each schema is shown below with its type and property counts.
pbl
object
1 property
404
object
1 property
threeDsAuthentication
object
Contains optional fields required by 3DS 2 authentication protocol.
7 properties
browser
object
Browser data required for 3DS 2 browser flow. If not provided, these data will be collected by PayU. It is strongly recommended to include it when charging a s…
9 properties9 required
properties
array
Array of objects related to transaction identification.
403
object
1 property
address
object
Section containing data about shipping address. Section is a single object of type address
7 properties
blikData
object
Additional data for BLIK payment with T6 or token.
7 properties
shippingMethod
object
Section containing data of shipping method. Section is a single object of type shippingMethod.
3 properties
products
array
Section containing data of the ordered products. Section products is an array of objects of type product.
payMethod
object
12 properties2 required
400
object
1 property
clickToPayVisa
object
Click to Pay data for Visa.
1 property1 required
delivery
object
Section containing delivery address. For a list of parameters, see section delivery
10 properties
wire
object
1 property
500
object
1 property
shoppingCarts
array
Array of objects related to transaction identification.
recurring
object
Additional information in case of a recurring payment.
2 properties
cardPlainData
object
5 properties
sdkEphemPubKey
object
Public key component of the ephemeral key pair generated by the 3DS SDK and used to establish session keys between the 3DS SDK and the issuer.
4 properties
donation
object
Section containing data of donation added to the order.
2 properties
card
object
1 property
billingAddress
object
5 properties
submerchant
object
1 property
blik
object
1 property
accountInformation
object
Informations about cardholders account.
17 properties
credit
object
Section containing credit data. This information is not required, but it is strongly recommended to include it. Otherwise the buyer will be prompted to provide…
3 properties
Partial
object
2 properties2 required
riskData
object
Contains optional fields required for risk analysis purposes. Required for BLIK with authorization code or token.
1 property1 required
sdk
object
Required if 3DS 2 is to be natively supported in your mobile app. Content needs to be generated by a certified 3DS 2 SDK. This information is not required, but…
6 properties6 required
clickToPay
object
ClickToPay details. When this node is used, set type to PBL and value to c. Provide exactly one option: visa or mastercard (not both).
shoppingCart
array
Section containing data of the ordered products. Section is an array of objects of type shoppingCart.
merchantRiskIndicator
object
Set of fields helping to assess risk connected with the order itself (type of goods purchased, shipping method etc.).
7 properties
settings
object
1 property
specificData
array
Additional data for some Visa Checkout integrations.
threeDsData
object
Object containing result data from 3DS process.
7 properties2 required
exemption
object
Merchant's preference regarding SCA exemption to be used to exempt card payment from 3DS authentication. Exclusive with challengeRequested. Requires additional…
3 properties2 required
cardholder
object
Describes cardholder's account data in merchant's possession, including details of account run for the cardholder in merchant's system You have to use ISO/IEC…
3 properties
401
object
1 property
merchantFunds
object
Indicates whether merchant's own funding (e.g. a gift card) has been used to partially pay for the order. Sum of amounts provided here and of field denote the…
2 properties2 required
mcpData
object
Section allows to pass currency conversion details if you chose to use Multi-Currency Pricing.
5 properties5 required
shippingMethods
array
Array of objects related to shipping method.
clickToPayMastercard
object
Click to Pay data for Mastercard.
2 properties2 required
buyer
object
Section containing buyer data.
9 properties
payMethods
object
Section allows to directly invoke payment method. Section payMethods is one object of payMethod type.
1 property
Full
null
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of PayU Order API, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.
