LayUp Technologies DebitOrderMandateService API

swagger: '2.0'
info:
  title: Layup endpoints AbsaDebiCheckService DebitOrderMandateService 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.

    '
host: localhost:3000
schemes:
- http
- https
- wss
consumes:
- application/json
produces:
- application/json
security:
- apiKey:
  - read
  - write
tags:
- name: DebitOrderMandateService
paths:
  /v1/debit-order-mandates:
    post:
      operationId: DebitOrderMandateService_create
      responses:
        '200':
          description: A successful response.
          schema:
            $ref: '#/definitions/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: body
        in: body
        required: true
        schema:
          $ref: '#/definitions/modelDebitOrderMandateCreateRequest'
      tags:
      - DebitOrderMandateService
  /v1/merchants/{merchantId}/debit-order-mandates:
    get:
      operationId: DebitOrderMandateService_get
      responses:
        '200':
          description: A successful response.
          schema:
            $ref: '#/definitions/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
        type: string
      tags:
      - DebitOrderMandateService
definitions:
  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
securityDefinitions:
  apiKey:
    type: apiKey
    name: apikey
    in: header