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

LayUp Technologies PaymentService API

The PaymentService API from LayUp Technologies — 10 operation(s) for paymentservice.

LayUp Technologies PaymentService API is one of 29 APIs that LayUp Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 13 operations across 10 paths, and defines 8 schemas. It is described by OpenAPI 2.0, at version 1.4.16.

Requests are made against the base URL https://api.layup.co.za.

13 operations 10 paths 8 schemas 2 DELETE6 GET4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.4.16
Base URL
https://api.layup.co.za
Authentication
API Key
Resource Areas
1

Authentication & Security 1

LayUp Technologies PaymentService API declares 1 security scheme for authenticating requests. An API key is passed in the header as apikey (apiKey). By default, every request must be authenticated.

Paths & Operations 13

Across 10 paths, the API surfaces 13 operations — 2 DELETE, 6 GET, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

PaymentService 13
GET
/v1/generate-refund
PaymentService_refund 6 params → 200204403404
GET
/v1/manual-refund
PaymentService_manualRefund 6 params → 200204403404
POST
/v1/offline-payments
PaymentService_CreateOffline 2 params → 200204403404
DELETE
/v1/offline-payments/{_id}
PaymentService_DeleteOffline 1 param → 200204403404
GET
/v1/payments
PaymentService_GetMany 19 params → 200204403404
DELETE
/v1/payments
PaymentService_Delete 1 param → 200204403404
POST
/v1/payments
PaymentService_Create 3 params → 200204403404
GET
/v1/payments/{_id}
PaymentService_Get 7 params → 200204403404
PUT
/v1/payments/{_id}
PaymentService_UpdateById 3 params → 200204403404
GET
/v1/realtime-refund
PaymentService_realtimeRefund 6 params → 200204403404
GET
/v1/refund-payments/{_id}
PaymentService_RefundPaymentMailer 1 param → 200204403404
POST
/v1/transfer-payments
PaymentService_TransferPayment 1 param → 200204403404
POST
/v1/undo-transfer-payments
PaymentService_UndoTransfer 1 param → 200204403404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are modelPaymentResponse (23 properties), modelPaymentRequest (17 properties), modelOfflinePaymentRequest (8 properties), modelPaymentRedirectResponse (5 properties). Each schema is shown below with its type and property counts.

modelPaymentResponseMany
object
1 property
modelPaymentRedirectResponse
object
5 properties
modelPaymentResponse
object
23 properties
modelConnectorData
object
Connector data bypasses protobuf conversion to allow any fields.
2 properties
modelOfflinePaymentRequest
object
8 properties
modelNameAndValue
object
2 properties
modelPaymentRequest
object
17 properties
modelTransferPaymentRequest
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

layup-technologies-paymentservice-api-openapi.yml Raw ↑

Other APIs LayUp Technologies publishes across the network.

LayUp Technologies AbsaDebiCheckService API
LayUp Technologies AbsaEftService API
LayUp Technologies authService API
LayUp Technologies BankService API
LayUp Technologies BankTransactionService API
LayUp Technologies CardService API
LayUp Technologies ConnectorService API
LayUp Technologies DebiCheckService API
LayUp Technologies DebitOrderMandateService API
LayUp Technologies IntegrationService API
LayUp Technologies InternationalMsisdnService API
LayUp Technologies InvoicesService API
Where this information came from

This is an independent, third-party profile of LayUp Technologies PaymentService 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.