How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

PayU Payout API

To widthraw funds from the PayU account you need to create a payout.

PayU Payout 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 Payout. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 1 JSON Schema.

This API exposes 2 operations across 2 paths, and defines 16 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.

2 operations 2 paths 16 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.1.0
Base URL
https://secure.payu.com
Authentication
HTTP Bearer, HTTP Basic
License
Resource Areas
1

Authentication & Security 2

PayU Payout 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 2

Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Payout 2

To widthraw funds from the PayU account you need to create a payout.

POST
/api/v2_1/payouts
Create a Payout
create-a-payout 2 params body → 201400401403404
GET
/api/v2_1/payouts/{payoutId}
Retrieve a Payout
retrieve-a-payout 3 params → 200400401403404

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are CardPayout (6 properties), payout (5 properties), customerAddress (5 properties), BankAccountPayout (5 properties). Each schema is shown below with its type and property counts.

401
object
1 property
MarketplacePayout
object
3 properties 3 required
FxPayout
object
4 properties 4 required
customerAddress
object
Payout recipient's name.
5 properties 1 required
400
object
1 property
404
object
1 property
403
object
1 property
BankAccountPayout
object
5 properties 4 required
account
object
Information about account to which payout should be sent.
3 properties 1 required
CardPayout
object
6 properties 4 required
fxData
object
Section containing details of the payout conversion.
5 properties 5 required
payout
object
Payout information.
5 properties 2 required
bankAddress
object
Bank address information.
4 properties
cardForPayout
object
Data of the card that the payout will be made to. Required in case of a payout to the card number .
3 properties 3 required
payee
object
Required section designed to limit the risk of fraud or money laundering.
4 properties 3 required
StandardPayout
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

payu-payout-api-openapi.yml Raw ↑

Other APIs PayU publishes across the network.

PayU India REST API
PayU Latam Payments API
PayU Enterprise API (PaymentsOS)
PayU Authorize API
PayU Card Installments API
PayU FX-Reference API
PayU Marketplace-Seller API
PayU Marketplace-Verification API
PayU MCP API
PayU Order API
PayU Partner-Merchant-Registration API
PayU Payment-Methods API
Where this information came from

This is an independent, third-party profile of PayU Payout 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.