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

Paga Collect API

NGN collections - payment requests and persistent payment accounts.

Paga Collect API is one of 5 APIs that Paga publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 8 operations across 8 paths, and defines 4 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against 4 base URLs: https://www.mypaga.com, https://beta.mypaga.com, https://collect.paga.com, https://beta-collect.paga.com.

8 operations 8 paths 4 schemas 8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://collect.paga.com
Authentication
HTTP Basic, API Key, API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 4

Paga Collect API declares 4 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as principal (pagaPrincipal). An API key is passed in the header as credentials (pagaCredentials). An API key is passed in the header as hash (pagaHash). By default, every request must be authenticated.

  • basicAuth — Collect API and Direct Debit API use HTTP Basic authentication with base64(publicKey:secretKey), where publicKey is the account principal and secretKey is the…
  • pagaPrincipal — Business API public key (principal / merchant public ID).
  • pagaCredentials — Business API secret key (credential / password).
  • pagaHash — SHA-512 hash of an operation-specific ordered concatenation of request parameters plus the account hash key. Required on every operation.

Paths & Operations 8

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

Collect 8

NGN collections - payment requests and persistent payment accounts.

POST
/paymentRequest
Register a payment request
requestPayment body → 200
POST
/status
Check payment request / mandate status
checkStatus body → 200
POST
/refund/v2
Refund or cancel a payment request (v2)
refundPaymentV2 body → 200
POST
/history
Retrieve collection history
retrieveHistory body → 200
POST
/registerPersistentPaymentAccount
Create a persistent payment account
registerPersistentPaymentAccount body → 200
POST
/getPersistentPaymentAccount
Retrieve a persistent payment account
getPersistentPaymentAccount body → 200
POST
/updatePersistentPaymentAccount
Update a persistent payment account
updatePersistentPaymentAccount body → 200
POST
/deletePersistentPaymentAccount
Delete a persistent payment account
deletePersistentPaymentAccount body → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are PaymentRequestRequest (11 properties), PersistentPaymentAccountRequest (8 properties), Party (5 properties), GenericResponse (4 properties). Each schema is shown below with its type and property counts.

Party
object
5 properties
GenericResponse
object
4 properties
PersistentPaymentAccountRequest
object
8 properties 3 required
PaymentRequestRequest
object
11 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

paga-collect-api-openapi.yml Raw ↑

Other APIs Paga publishes across the network.

Paga Connect
Paga Business API
Paga Direct Debit API
Paga Reference API
Where this information came from

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