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.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/layup-technologies-debitordermandateservice-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Layup endpoints AbsaDebiCheckService Debit Order Mandate 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: DebitOrderMandateService
paths:
  /v1/debit-order-mandates:
    post:
      operationId: DebitOrderMandateService_create
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/modelDebitOrderMandateResponse'
        '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:
      - DebitOrderMandateService
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/modelDebitOrderMandateCreateRequest'
        required: true
  /v1/merchants/{merchantId}/debit-order-mandates:
    get:
      operationId: DebitOrderMandateService_get
      responses:
        '200':
          description: A successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/modelDebitOrderMandateResponse'
        '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.
      parameters:
      - name: merchantId
        in: path
        required: true
        schema:
          type: string
      tags:
      - DebitOrderMandateService
components:
  schemas:
    modelDebitOrderMandateResponse:
      type: object
      properties:
        mandateId:
          type: string
        merchantId:
          type: string
        reference:
          type: string
        holderName:
          type: string
        holderSurname:
          type: string
        contact:
          type: string
        accountType:
          type: string
        accountNumber:
          type: string
        branchCode:
          type: string
        identificationType:
          type: string
        identificationNumber:
          type: string
    modelDebitOrderMandateCreateRequest:
      type: object
      properties:
        merchantId:
          type: string
        reference:
          type: string
        holderName:
          type: string
        holderSurname:
          type: string
        contact:
          type: string
        accountType:
          type: string
        accountNumber:
          type: string
        branchCode:
          type: string
        identificationType:
          type: string
        identificationNumber:
          type: string
  securitySchemes:
    apiKey:
      type: apiKey
      name: apikey
      in: header