PayU Latam Payments API
63
AI ReadinessAI-Aware (B-)63/100
Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey6 EndpointsREST
For Agents
Submit payments, query transaction statuses, and process refunds for Latin American merchants across cards, bank transfers, and local cash methods.
Use for: I need to process a card payment in Colombia, I want to check the status of a LatAm transaction, Retrieve the list of available banks for PSE transfers, Find the transaction details by order ID
Not supported: Does not handle subscription management, invoicing, or payouts - use for payment submission and transaction queries only.
PayU Latam Payments API provides payment processing for merchants across Latin America. It supports credit and debit card transactions, bank transfers, QR code payments, and cash-based payment methods specific to each LatAm country. The API handles payment submission, authorization, capture, and transaction queries across Brazil, Mexico, Colombia, Argentina, Chile, Peru, and Panama with local currency settlement.
Install Jentic One Beta
Connect the PayU Latam Payments API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PayU Latam Payments API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpayulatam.com%2Fpayulatam" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpayulatam.com%2Fpayulatam" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with PayU Latam Payments API.
Submit card, bank transfer, and cash payments across 7 Latin American countries
Query transaction status and details by order ID, reference code, or transaction ID
Process authorizations with deferred capture for card transactions
Retrieve available bank lists for bank transfer payment methods
Verify API connectivity and merchant credential validity via ping
Handle local payment methods including OXXO, Boleto, PSE, and Baloto
Use Cases
Patterns agents use PayU Latam Payments API for, with concrete tasks.
★ Latin American Card Payments
Process credit and debit card payments for customers across Latin America. PayU handles local acquiring in Brazil, Mexico, Colombia, Argentina, Chile, Peru, and Panama with support for Visa, Mastercard, AMEX, and local brands like Elo and Hipercard. Merchants submit payment requests via POST /payments-api/4.0/service.cgi with card details, amount, and currency. PayU returns authorization status with fraud screening results.
Submit a card payment for 150000 COP (Colombian Pesos) with card number, expiry, and buyer details via POST /payments-api/4.0/service.cgi using the SUBMIT_TRANSACTION command
Local Cash and Bank Transfer Methods
Accept payments through cash vouchers and bank transfers popular in each LatAm market. PayU supports OXXO and SPEI in Mexico, Boleto Bancario in Brazil, PSE bank transfers in Colombia, and similar local methods. Each method generates a payment reference or voucher that the customer pays at a physical location or through their bank's online portal.
Create a PSE bank transfer payment for 80000 COP, retrieve the available banks list via POST /payments-api/4.0/service.cgi#getBanksList, and redirect the customer to the selected bank
Transaction Queries and Reporting
Look up transaction details and status across multiple query methods. PayU provides transaction queries by order ID, reference code, and transaction ID through dedicated report endpoints. This enables reconciliation, customer support lookups, and automated status monitoring for payment operations across all supported Latin American markets.
Query the transaction status for reference code 'REF-2024-MX-001' via POST /reports-api/4.0/service.cgi#queryByReferenceCode and return the payment state and amount
AI Agent Payment Operations via Jentic
AI agents use the PayU Latam API through Jentic to submit payments, query transactions, and manage LatAm payment flows without handling raw merchant credentials. Agents search by intent, receive typed schemas for PayU's command-based API structure, and execute calls with Jentic managing the apiLogin and apiKey injection. This enables automated payment workflows across 7 Latin American countries.
Search Jentic for 'process payment in Colombia', load the schema for POST /payments-api/4.0/service.cgi, and execute a SUBMIT_TRANSACTION command for 50000 COP
Key Endpoints
6 endpoints — payu latam payments api provides payment processing for merchants across latin america.
METHOD
PATH
DESCRIPTION
POST
/payments-api/4.0/service.cgi
Submit a payment transaction
POST
/payments-api/4.0/service.cgi#getBanksList
Retrieve available banks for transfers
POST
/payments-api/4.0/service.cgi#ping
Test API connectivity
POST
/reports-api/4.0/service.cgi#queryByOrderId
Query transaction by order ID
POST
/reports-api/4.0/service.cgi#queryByReferenceCode
Query transaction by reference code
POST
/reports-api/4.0/service.cgi#queryByTransactionId
Query transaction by transaction ID
POST
/payments-api/4.0/service.cgi
Submit a payment transaction
POST
/payments-api/4.0/service.cgi#getBanksList
Retrieve available banks for transfers
POST
/payments-api/4.0/service.cgi#ping
Test API connectivity
POST
/reports-api/4.0/service.cgi#queryByOrderId
Query transaction by order ID
POST
/reports-api/4.0/service.cgi#queryByReferenceCode
Query transaction by reference code
POST
/reports-api/4.0/service.cgi#queryByTransactionId
Query transaction by transaction ID
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
PayU Latam Payments API
- AI-Aware (B-)63/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility44
AI-Readiness & Agent Experience94
Agent Usability50
Security69
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
44
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
42%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
83%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
69
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
69%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the PayU Latam Payments API by hand means learning its command-based service.cgi structure, placing apiLogin and apiKey in the request payload, and choosing the sandbox or production host yourself. Through Jentic you install once, import PayU Latam from the API Directory, store the merchant credentials once, and your agent calls it.
Permission scoping
PayU Latam sends its command and target details in the request body of a single service endpoint, so scope the agent by the operations it needs, such as querying an order by id or reference code. You choose that set, so payment submission is not included unless you add it.
Credential isolation
Your PayU Latam apiLogin and apiKey are stored once, encrypted, by your own Jentic One instance and injected into the request payload at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'process a payment in Colombia' or 'query an order by reference code', and Jentic returns the matching PayU Latam operation with its input schema for the command-based structure so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Global payment processor expanding into LatAm but with fewer local cash methods
Choose Stripe when the merchant needs global coverage and LatAm-specific cash methods are secondary to card processing.
FAQs
Specific to using PayU Latam Payments API through Jentic.
What authentication does the PayU Latam API use?
The PayU Latam API uses merchant authentication with apiLogin and apiKey credentials included in the request body of each API call. Through Jentic, these credentials are stored encrypted and injected automatically into the request payload so agents do not handle raw merchant keys.
Which countries does the PayU Latam API support?
PayU Latam supports merchants in Brazil, Mexico, Colombia, Argentina, Chile, Peru, and Panama. Each country has specific local payment methods available alongside international card brands. The API endpoint and account ID vary by country.
What are the rate limits for the PayU Latam API?
PayU Latam applies per-merchant rate limits of approximately 100 transactions per minute for payment submissions. Report query endpoints have separate limits. High-volume merchants can request increased thresholds through their PayU account manager.
How do I query a transaction status through Jentic?
Search Jentic for 'query PayU transaction', load the schema for POST /reports-api/4.0/service.cgi#queryByReferenceCode, and execute with the reference code. Jentic injects your apiLogin and apiKey automatically and returns the transaction state, amount, and payment method details.
Does the PayU Latam API support cash payment methods?
Yes. PayU supports cash-based methods including OXXO in Mexico, Boleto Bancario in Brazil, Baloto and Efecty in Colombia, and PagoEfectivo in Peru. Each method generates a voucher or reference code that the customer pays at a physical location within a defined expiry window.
Can I limit what my agent is allowed to do with the PayU Latam Payments API?
Yes. Because you run Jentic One yourself, your own rules decide which PayU Latam operations and merchant credentials the agent may use. Since PayU Latam sends its command and target in the request body of one service endpoint, you scope the agent to the specific operations it needs, such as querying a transaction by order ID or reference code. Payment submission is not available to the agent unless you explicitly add it to that allowed set.
GET STARTED