Skip Pay solution: From testing to production
Welcome to the implementation guide for Skip Pay, the payment solution that simplifies and accelerates payouts for your business. This guide is designed to help you implement Skip Pay smoothly and efficiently, and to ensure that you have all the information you need to get started.
Before beginning the implementation process, it is important to note that Skip Pay has a checklist of requirements that must be met before starting to use our services in a production environment. These requirements are in place to ensure that your business is properly set up to use our platform and to ensure a smooth implementation process.
In addition to the checklist, there are also technical requirements that must be met before your business can start using Skip Pay. Our technical team can help you ensure that your systems are properly configured to integrate with our platform.
Once all requirements are met, we will walk you through the implementation process step by step. This guide will cover everything you need to know to integrate Skip Pay into your business processes, including technical details and best practices.
We understand that implementing a new payment solution can be complex and time-consuming, but our goal is to make the process as smooth and easy as possible. By following this guide, you'll be well on your way to using Skip Pay to simplify your applications and improve your operational efficiency.
General information
This section provides an overview of important information related to the implementation and use of Skip Pay services. It includes details on how to access the administration portal for partners as well as technical requirements for using Skip Pay services. Additionally, this section covers key rules and policies related to customer applications and orders. It is recommended that partners review this section thoroughly before implementing Skip Pay services:
- As a partner, you'll need to use our back office administration tool to manage your account. You can access the back office at https://admin.skippay.dev. Please note that skippay.dev is for testing purposes and skippay.cz is a production environment.
- To log in, use your unique email address and password. We also require two-factor authentication, which is currently set to the code '123456' in the testing environment.
- To verify an application, we use a one-time password (OTP) that is sent via SMS. The default OTP is '123456'. In test mode, SMS is not sent; therefore, the code '123456' is used to demonstrate the OTP function in the testing environment.
Our important rules
Here are some important rules to keep in mind when submitting applications:
- Applications are paired internally based on the customer's unique email address and phone number.
- We have a "first unpaid application" rule: if a customer has a first application (order) that's unpaid, any subsequent applications will be rejected. The customer must pay for their first application before submitting another one. A customer can't have an active (approved but unpaid) application for both deferred payment and third-party financing at the same time.
- As a partner, you can access our API endpoint at api.partner.skippay.dev To log in, use your unique email address and password. You can find the API documentation at https://developers.skippay.cz.
If you are not creating another order for a known customer, use a unique email and phone number that you can create, for example, using a random nine-digit number generator, where you insert a random number into the randomNumber variable. You can then send the email in the format hello.world+randomNumber@skippay.cz and the phone number in the format +420randomNumber.
Our technical requirements
| Service | Integration environment |
|---|---|
| Frontend environment (Web & Self-care) | skippay.dev |
| Backend (Back office) | admin.skippay.dev |
| API – for partners | api.partner.skippay.dev |
| Developer portal | developers.skippay.cz |
Our checklist to successfully start Skip Pay services
To ensure that you can start using Skip Pay services smoothly, make sure you have successfully completed all the steps below:
- Sign up for the API through the REST API user interface and communicate with the API.
- Create a new application with the status "Approved".
- Create a new application with the status "Cancelled".
- All items in the order can be switched to the "Sent", "Delivered" or "Cancelled" status.
- The order is in the "Sent", "Delivered" or "Cancelled" status.
- All items in the order can be switched to the "Returned" status.
- The order is in the "Returned" status.
- The applications created can be viewed in the administration interface.
- Pre-check returns different results (if implemented).
- Successfully received notifications using our API for your applications.
Payment methods available in this guide
In this guide, we will discuss two application methods offered by Skip Pay:
- Skip Pay Deferred application: This payment method allows the customer to defer payment for goods for up to 50 days.
- Skip Pay in Three application: This payment method allows the customer to split the payment into three monthly installments.
Price ranges vary according to your needs. We are happy to go into as much detail as you would like regarding your unique needs.
To distinguish between these payment methods in your application, use the "Type" attribute, which can have the values DEFERRED_PAYMENT or PAY_IN_THREE.
Testing process
Approved and rejected applications
To ensure that Skip Pay is working correctly, it's important to test its functionality. Here are the steps to test the process for applications with the "Approved" and "Rejected" statuses.
If you are not sure how to create a new application, please follow this guide where we explain the whole process.
If you need to check the status of an application, you can use the API endpoint /financing/v1/applications/applicationId, where 'applicationId' is the unique ID of the application. Simply send an empty GET request to this endpoint to retrieve detailed information about the application.
Approved Deferred application
- Use Skip Pay REST API to create applications.
- Create an application with a total price of < 1000.
- Verify the application.
- The "state" parameter should contain the value "READY" and the "stateReason" parameter should contain the value "READY_TO_SHIP".
Rejected Deferred application
- Use Skip Pay REST API to create applications.
- Create an application with an email address containing the string “reject”, for example: hello.world+reject@skippay.cz.
- After verification of the application, the “state” parameter must contain the value REJECTED and the 'stateReason' parameter must contain the value REJECTED.
Approved Pay in three applications
-
Use Skip Pay REST API to create applications.
-
The application (order) must be within the allowed price range of 3000 CZK - 15000 CZK.
-
For the payment of the first installment, use the test payment card:
- Card number: 4000007000010006
- Expiration date: any valid date
- Verification code: any 3 numbers
-
After completing the process, a page will display with information about the successful completion of the third party.
-
After the application is verified, the state parameter must contain the value READY and the stateReason parameter must contain the value READY_TO_SHIP.
Rejected Pay in three application
- Use Skip Pay REST API to create applications.
- The application (order) must be out of the allowed price range of 3000 CZK - 15000 CZK, for example 1000 CZK.
- When passing through, the customer is redirected to a page with information about the rejection of the application.
- After the application is verified, the state parameter must contain the value REJECTED and the stateReason parameter must contain the value REJECTED.
Switching application statuses (Deferred Payment and Pay in three)
To update the status of individual items in an order, use the "Mark order items as cancelled/sent/delivered/returned" methods. The API endpoints for this method are:
An order is in the "Cancelled," "Sent," "Delivered," or "Returned" state when all items in the order are in the same state.
For example, an order is in the 'Sent' state when the Partner has marked the order or all items in the order as sent.
Summary
Congratulations on completing the testing process for the Skip Pay financing application! During the testing process, you have learned about the different stages of the application process and how to test each stage effectively. You have also become familiar with the different API endpoints and their corresponding functions.
As a result of your testing, you have gained valuable insights into the performance and functionality of the Skip Pay financing application. You have identified areas for improvement and have made recommendations for optimizing the application's performance and user experience.