Riverty BNPL Order Management API
67
AI ReadinessAI-Aware (B+)67/100
Official vendor OpenAPI document · agent-readyPaymentsBilling SubscriptionsapiKey6 EndpointsREST
For Agents
Programmatically get available payment methods, authorize a payment. Covers 6 operations with apiKey authentication.
Use for: I need to available payment methods, I want to authorize a payment, Search for capture a payment, Find all refund a payment
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Riverty Buy Now, Pay Later (BNPL) API for payment authorization, capture, refund, void, and order management. Supports multiple payment types including invoices, installments, and direct debit across European markets. The API exposes 6 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Riverty BNPL Order Management API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Riverty BNPL Order Management 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%2Friverty.com%2Friverty" | 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%2Friverty.com%2Friverty" | 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 Riverty BNPL Order Management API.
Get available payment methods
Authorize a payment
Capture a payment
Refund a payment
Void an authorization
Update an order
Use Cases
Patterns agents use Riverty BNPL Order Management API for, with concrete tasks.
★ Payments Operations
Use the Riverty BNPL Order Management API to perform payments operations programmatically. The API provides 6 endpoints covering core functionality including get available payment methods, authorize a payment, capture a payment.
Call POST /api/v3/checkout/payment-methods to get available payment methods
Automated Checkout Management
Automate checkout operations by combining multiple Riverty BNPL Order Management API endpoints. Agents can authorize a payment and then capture a payment in a single workflow.
Call POST /api/v3/checkout/authorize to authorize a payment, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Riverty BNPL Order Management API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'get available payment methods', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
6 endpoints — riverty buy now, pay later (bnpl) api for payment authorization, capture, refund, void, and order management.
METHOD
PATH
DESCRIPTION
POST
/api/v3/checkout/payment-methods
Get available payment methods
POST
/api/v3/checkout/authorize
Authorize a payment
POST
/api/v3/orders/{orderNumber}/captures
Capture a payment
POST
/api/v3/orders/{orderNumber}/refunds
Refund a payment
POST
/api/v3/orders/{orderNumber}/voids
Void an authorization
POST
/api/v3/orders/{orderNumber}/updateOrder
Update an order
POST
/api/v3/checkout/payment-methods
Get available payment methods
POST
/api/v3/checkout/authorize
Authorize a payment
POST
/api/v3/orders/{orderNumber}/captures
Capture a payment
POST
/api/v3/orders/{orderNumber}/refunds
Refund a payment
POST
/api/v3/orders/{orderNumber}/voids
Void an authorization
POST
/api/v3/orders/{orderNumber}/updateOrder
Update an order
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.
R
Riverty BNPL Order Management API
- AI-Aware (B+)67/100
100
Foundational Compliance69
Developer Experience & Jentic Compatibility51
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
98%
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.
69
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.
75%
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.
51
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
54%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
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 Riverty BNPL Order Management API by hand means setting your Riverty apiKey in the Authorization header, choosing between the production and sandbox hosts, and posting captures, refunds, and voids against each order yourself. Through Jentic you install once, import the Riverty BNPL Order Management API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Riverty puts the order number in the URL path (/api/v3/orders/{orderNumber}/captures), so a rule can pin your agent to one order: it can capture or update that order and nothing else. You choose the operations it may call, so money-moving ones like refunds or voids are not included unless you add them.
Credential isolation
Your Riverty API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get available payment methods' or 'capture an order', and Jentic returns the matching Riverty BNPL Order Management API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using Riverty BNPL Order Management API through Jentic.
What authentication does the Riverty BNPL Order Management API use?
The Riverty BNPL Order Management API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get available payment methods with the Riverty BNPL Order Management API?
Yes. Use the POST /api/v3/checkout/payment-methods endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Riverty BNPL Order Management API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get available payment methods through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get available payment methods'. Jentic returns the matching Riverty BNPL Order Management API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Riverty BNPL Order Management API have?
The Riverty BNPL Order Management API exposes 6 endpoints covering checkout, orders operations.
Can I limit what my agent is allowed to do with the Riverty BNPL Order Management API?
Yes. Riverty puts the order number in the URL path, such as /api/v3/orders/{orderNumber}/captures, so a rule you set in your self-hosted Jentic One instance can pin the agent to a single order and let it capture or update only that order. You also choose which of the six operations the agent may call, so money-moving actions like refunds and voids stay out of reach unless you explicitly grant them. Because Jentic One runs under your control, your own rules decide which operations and stored credentials the agent uses at execution time.
GET STARTED