Skip to main content

Create application

POST 
/financing/v1/applications

Elementary flow starts when customer wants to use one of Skip Pay's payment method for financing his purchase made in partner e-shop.

Financing typeSupported
DEFERRED_PAYMENTYES
PAY_IN_THREEYES

Use /financing/v1/applications resource with properly filled request that contains at least following data

  • Customer information

    • Name (first name and last name - if possible, otherwise full name)
    • E-mail
    • Phone number

  • Order details

    • Number
    • Total Price (including VAT)
    • Total VAT (array of total amounts split by VAT rates)
    • Order items (array, at least one item is required)
      • Code
      • Order item name
      • Total price (all pieces, including VAT)
      • Total VAT

  • Additional information necessary for the continuation and completion of the process

    • Your URL where the customer should be redirected after application approval
    • Your URL where the customer should be redirected after application rejection
    • URL of your notification endpoint you want us to send you notifications about particular application updates

For best customer experience request should contain following data:

  • Customer information

    • Fraud prevention data
      • Historical count of customer's transactions made in partner's e-shop

  • Order details

    • Delivery carrier information
    • Address (type BILLING)
      • Country
      • City
      • Street
      • Street number
      • ZIP
      • Address type
    • Order items
      • Image

  • Personal data processing and terms and conditions agreement

If the request was successfully processed, you receive HTTP status code 201 and application object with following important information in the response:

  • Application unique ID

  • Application state

  • Application substate

  • Gateway redirect URL where you should redirect a customer after processing of the response

  • Recurrence ID if you sent isRecurring=true in request (for recurring orders)

If the request was recognized as duplication, you receive HTTP status code 200 and the application object created during the first related successful request.

Note: If the optional agreementTermsAndConditions field was not sent with the request (or it was sent with a value of false), the application will be created with agreementTermsAndConditions value set to false, state PROCESSING and stateReason PROCESSING_REDIRECT_NEEDED.

In other cases, you may receive errors similar to the following ones:

Status codeCodeExplanation
400INVALID_REQUESTRequest was not well formatted (malformed request syntax, size too large, etc.)
422UNPROCESSABLERequest was well-formed but was unable to be followed due to semantic errors

Request​

Responses​

Application data is duplicate. Existing application is returned.