LayUp Technologies PayAtService API
The PayAtService API from LayUp Technologies — 5 operation(s) for payatservice.
The PayAtService API from LayUp Technologies — 5 operation(s) for payatservice.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/layup-technologies-payatservice-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Layup endpoints AbsaDebiCheckService Pay At Service API
version: 1.4.16
description: 'Welcome to The Layup Swagger page. This page allows developers to interactively explore the API. For more detailed documentation see [The Layup documentation page](https://documentation.layup.co.za/).
# Introduction
## What is LayUp
LayUp is a lay-by payment solution. LayUp Schedules payments and ensures that your clients pay securely, effectively and on time. Depending on your parameters LayUp schedules a payment plan for your clients. Once a payment plan has been completed we notify you. There are 3 stories that are of importance to a merchant:
1. Order Creation
2. Deposit Received (and holding Stock for your client)
3. Order Completion.
LayUp allows you to take full control over the entire payment process if you wish to do so. We also provide a convenient front-end for users to use. The front-end should significantly reduce the time to integrate and get you started using LayUp as soon as possible.
Once an order is completed a notification will be sent to the merchant so that you can provide the client with their product.
## How to use LayUp
As a merchant who wants to place an order through LayUp, you want to send the relevant information to the LayUp API to create the order. The API will return an order ID. Unless your integration is using a custom user interface, you want to send the user to the LayUp customer payment widget. The URL for this widget is <u>https://shopper.layup.co.za/order/{orderId}</u> for production and <u>https://sandbox.layup.co.za/order/{orderId}</u> for sandbox.
'
servers:
- url: http://localhost:3000
- url: https://localhost:3000
- url: wss://localhost:3000
security:
- apiKey:
- read
- write
tags:
- name: PayAtService
paths:
/v1/payAt/adviseTransaction:
post:
operationId: PayAtService_adviseTransaction
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/modelPayAtTransactionAdviceResponse'
'204':
description: Successfully processed the request, no content.
'403':
description: Returned when the user does not have permission to access the resource.
'404':
description: Returned when the resource does not exist.
tags:
- PayAtService
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/modelPayAtTransactionAdviceRequest'
required: true
/v1/payAt/authorize:
post:
operationId: PayAtService_authorize
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/modelPayAtAuthorizationResponse'
'204':
description: Successfully processed the request, no content.
'403':
description: Returned when the user does not have permission to access the resource.
'404':
description: Returned when the resource does not exist.
tags:
- PayAtService
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/modelPayAtAuthorizationRequest'
required: true
/v1/payAt/echoTest:
post:
operationId: PayAtService_echoTest
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/modelPayAtEchoTestResponse'
'204':
description: Successfully processed the request, no content.
'403':
description: Returned when the user does not have permission to access the resource.
'404':
description: Returned when the resource does not exist.
tags:
- PayAtService
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/modelPayAtEchoTestRequest'
required: true
/v1/payAt/enquire:
post:
operationId: PayAtService_enquiry
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/modelPayAtEnquiryResponse'
'204':
description: Successfully processed the request, no content.
'403':
description: Returned when the user does not have permission to access the resource.
'404':
description: Returned when the resource does not exist.
tags:
- PayAtService
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/modelPayAtEnquiryRequest'
required: true
/v1/payAt/reverseAuthorization:
post:
operationId: PayAtService_reverseAuthorization
responses:
'200':
description: A successful response.
content:
application/json:
schema:
$ref: '#/components/schemas/modelPayAtReverseAuthorizationResponse'
'204':
description: Successfully processed the request, no content.
'403':
description: Returned when the user does not have permission to access the resource.
'404':
description: Returned when the resource does not exist.
tags:
- PayAtService
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/modelPayAtReverseAuthorizationRequest'
required: true
components:
schemas:
modelPayAtAuthorizationRequest:
type: object
properties:
messageID:
type: string
transmissionDateTime:
type: string
securityData:
$ref: '#/components/schemas/modelPayAtSecurityData'
accountNumber:
type: string
amount:
type: integer
format: int32
networkTransactionID:
type: string
networkData:
$ref: '#/components/schemas/modelPayAtNetworkData'
modelPayAtNetworkData:
type: object
properties:
networkId:
type: integer
format: int32
networkName:
type: string
modelPayAtEnquiryResponse:
type: object
properties:
amount:
type: integer
format: int32
dueDate:
type: string
exactAmount:
type: boolean
messageID:
type: string
transmissionDateTime:
type: string
securityData:
$ref: '#/components/schemas/modelPayAtSecurityData'
accountNumber:
type: string
networkData:
$ref: '#/components/schemas/modelPayAtNetworkData'
customerData:
$ref: '#/components/schemas/modelPayAtCustomerData'
responseText:
type: string
responseCode:
type: string
modelPayAtCustomerData:
type: object
properties:
firstName:
type: string
lastName:
type: string
modelPayAtReverseAuthorizationRequest:
type: object
properties:
messageID:
type: string
transmissionDateTime:
type: string
securityData:
$ref: '#/components/schemas/modelPayAtSecurityData'
accountNumber:
type: string
amount:
type: integer
format: int32
networkTransactionID:
type: string
networkData:
$ref: '#/components/schemas/modelPayAtNetworkData'
issuerTransactionID:
type: string
repeatIndicator:
type: boolean
modelPayAtTransactionAdviceRequest:
type: object
properties:
messageID:
type: string
transmissionDateTime:
type: string
securityData:
$ref: '#/components/schemas/modelPayAtSecurityData'
accountNumber:
type: string
amount:
type: integer
format: int32
tenderType:
type: string
repeatIndicator:
type: boolean
networkTransactionID:
type: string
networkData:
$ref: '#/components/schemas/modelPayAtNetworkData'
issuerTransactionID:
type: string
modelPayAtEchoTestRequest:
type: object
properties:
securityData:
$ref: '#/components/schemas/modelPayAtSecurityData'
messageID:
type: string
transmissionDateTime:
type: string
echoData:
type: string
modelPayAtTransactionAdviceResponse:
type: object
properties:
messageID:
type: string
transmissionDateTime:
type: string
securityData:
$ref: '#/components/schemas/modelPayAtSecurityData'
accountNumber:
type: string
tenderType:
type: string
repeatIndicator:
type: boolean
amount:
type: integer
format: int32
networkData:
$ref: '#/components/schemas/modelPayAtNetworkData'
networkTransactionID:
type: string
issuerTransactionID:
type: string
responseCode:
type: string
responseText:
type: string
modelPayAtSecurityData:
type: object
properties:
login:
$ref: '#/components/schemas/modelPayAtLoginData'
modelPayAtReverseAuthorizationResponse:
type: object
properties:
messageID:
type: string
transmissionDateTime:
type: string
securityData:
$ref: '#/components/schemas/modelPayAtSecurityData'
accountNumber:
type: string
networkData:
$ref: '#/components/schemas/modelPayAtNetworkData'
networkTransactionID:
type: string
responseCode:
type: string
responseText:
type: string
issuerTransactionID:
type: string
repeatIndicator:
type: boolean
customerData:
$ref: '#/components/schemas/modelPayAtCustomerData'
modelPayAtEnquiryRequest:
type: object
properties:
messageID:
type: string
transmissionDateTime:
type: string
securityData:
$ref: '#/components/schemas/modelPayAtSecurityData'
accountNumber:
type: string
amount:
type: integer
format: int32
networkData:
$ref: '#/components/schemas/modelPayAtNetworkData'
modelPayAtEchoTestResponse:
type: object
properties:
messageID:
type: string
transmissionDateTime:
type: string
securityData:
$ref: '#/components/schemas/modelPayAtSecurityData'
echoData:
type: string
responseCode:
type: string
responseText:
type: string
modelPayAtLoginData:
type: object
properties:
loginID:
type: string
password:
type: string
modelPayAtAuthorizationResponse:
type: object
properties:
messageID:
type: string
transmissionDateTime:
type: string
securityData:
$ref: '#/components/schemas/modelPayAtSecurityData'
accountNumber:
type: string
networkData:
$ref: '#/components/schemas/modelPayAtNetworkData'
networkTransactionID:
type: string
responseCode:
type: string
responseText:
type: string
issuerTransactionID:
type: string
customerData:
$ref: '#/components/schemas/modelPayAtCustomerData'
securitySchemes:
apiKey:
type: apiKey
name: apikey
in: header