OPay Payments API
Server-to-server payment creation across payment methods.
OPay Payments API is one of 3 APIs that OPay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 1 operation across 1 path, and defines 10 schemas. It is described by OpenAPI 3.0.3, at version 1.0.
Requests are made against 2 base URLs: https://liveapi.opaycheckout.com/api/v1/international, https://testapi.opaycheckout.com/api/v1/international.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
OPay Payments API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (PublicKeyAuth).
It accepts HTTP bearer tokens (SignatureAuth).
PublicKeyAuth— Bearer token = merchant public key (used for cashier/create).SignatureAuth— Bearer token = HMAC-SHA512 of the JSON request body signed with the merchant private key.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
Server-to-server payment creation across payment methods.
Schemas 10
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are PaymentCreateRequest (11 properties), BankCard (6 properties), NextAction (5 properties), UserInfo (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from OPay 2
Other APIs OPay publishes across the network.
This is an independent, third-party profile of OPay Payments 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.