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

GSMA Payment API

Operations to obtain information about payments

GSMA Payment API is one of 31 APIs that GSMA publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payment. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a changelog.

This API exposes 2 operations across 2 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version wip.

Requests are made against a single base URL, {apiRoot}/carrier-billing/vwip.

2 operations 2 paths 10 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wip
Base URL
https://sandbox.mobilemoneyapi.io/simulator/v1.2/passthrough/mm
Authentication
OpenID Connect, HTTP Bearer
License
Resource Areas
1

Authentication & Security 2

GSMA Payment API declares 2 security schemes for authenticating requests. It supports OpenID Connect (openId) discovered at https://example.com/.well-known/openid-configuration. It accepts HTTP bearer tokens ({$request.body#/sinkCredential.credentialType}) (notificationsBearerAuth).

Paths & Operations 2

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

Payment 2

Operations to obtain information about payments

GET
/payments
Get a list of payments
retrievePayments 8 params → 200400401403429
GET
/payments/{paymentId}
Get payment details
retrievePayment 2 params → 200400401403404429

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ChargingMetaData (7 properties), PaymentItem (6 properties), Payment (6 properties), AmountTransaction (6 properties). Each schema is shown below with its type and property counts.

ErrorInfo
object
3 properties 3 required
XCorrelator
string
ChargingMetaData
object
7 properties
ChargingInformation
object
5 properties 3 required
PaymentItem
object
6 properties 4 required
PaymentAmountForCharge
object
3 properties 1 required
PaymentDetails
array
Detailed description of the concepts/items considered within a specific payment procedure.
Payment
object
6 properties 4 required
PaymentArray
array
A list of payment(s)
AmountTransaction
object
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

gsma-payment-api-openapi.yml Raw ↑

Other APIs GSMA publishes across the network.

GSMA Accounts API
GSMA Authorisation Codes API
GSMA Bills API
GSMA Call Forwarding information retrieval API
GSMA Check Device Swap API
GSMA Check SIM Swap API
GSMA Debit Mandates API
GSMA Device reachability status API
GSMA Discovery API
GSMA Get Device Identifiers API
GSMA Home Devices QoD API
GSMA Links API
Where this information came from

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