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

NALA Payment Account API

The Payment Account API from NALA — 1 operation(s) for payment account.

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

Tagged areas include Payment Account. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 2 operations across 1 path, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://rest.sandbox.rafiki-api.com/v1.

2 operations 1 paths 18 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://rest.prod.rafiki-api.com/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

NALA Payment Account API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Bearer).

Paths & Operations 2

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

Payment Account 2
GET
/payment-accounts
List
2 params → 200422500
POST
/payment-accounts
Get or create
body → 200201422500

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are openapi.PaymentAccountGetOrCreateResponse (7 properties), openapi.PaymentAccountGetOrCreateRequest (5 properties), openapi.ResponseBodyValidationFailed (3 properties), openapi_PaymentAccountGetOrCreateResponse_mobile_money (2 properties). Each schema is shown below with its type and property counts.

openapi_PaymentAccountGetOrCreateRequest_bank_account
object
2 properties
openapi_PaymentAccountGetOrCreateRequest_mobile_money
object
2 properties
openapi.PaymentAccountGetOrCreateRequest
object
5 properties
openapi.ResponseBodyInternalServerError
object
2 properties
openapi.ResponseBodyValidationFailed
object
3 properties
openapi.PaymentAccountListResponseMeta
object
1 property
openapi_PaymentAccountGetOrCreateResponse_bank_account
object
2 properties
openapi.ResponseBodySuccessCollection
object
2 properties
_payment_accounts_post_200_response
openapi.PaymentAccountGetOrCreateResponse
object
7 properties
openapi_PaymentAccountGetOrCreateResponse_holder
object
2 properties
openapi_PaymentAccountListResponseMeta_paging_cursors
object
1 property
openapi_ResponseBodyValidationFailed_errors
object
1 property
openapi_PaymentAccountGetOrCreateRequest_holder
object
required The individual (or business) in whose name the bank account is registered
2 properties
_payment_accounts_get_200_response
openapi_PaymentAccountListResponseMeta_paging
object
2 properties
openapi.ResponseBodySuccessNoMeta
object
1 property
openapi_PaymentAccountGetOrCreateResponse_mobile_money
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nala-payment-account-api-openapi.yml Raw ↑

Other APIs NALA publishes across the network.

NALA Bank API
NALA Lookup API
NALA Payout API
NALA Wallet API
Where this information came from

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