Plugin icon



Ensuring you have satisfied our specific requirements for each feature of the integration is key to being quickly certified

Unit Tests

It is important that the unit tests be implemented and should focus on testing one specific feature. This helps to keep the initial focus only on what a given unit of code is doing, not what its dependencies do

End to End Tests

End to End tests are important for testing the purchase flow as a whole and bringing each of the independent code units together. This is where dependencies come into play and edge case issues can be more easily identified

This piece is also key in understanding how Zip will fit in with your existing e-commerce pipeline. Everything, starting from the initial customer checkout, all the way to consuming disbursement and financial data should be tested to ensure Zip transactions flow smoothly all the way through

Product Awareness & Conversion Optimisation

As a part of all Zip integrations, a key element has been identified as vital to increased checkout and conversions. As such, as a part of our partnerships we include this as a requirement when integrating Zip as an online payment method


There are a number of outcomes when transacting with Zip at checkout, from existing customers to new customers, to those who are not able to provide an instant result.

There are also several scenarios that require different items or values to be passed in the API calls. These will need to match our spec for their respective scenarios for certification. Each of these are listed below and must be handled for a complete integration:

  1. Complete an order creating a new Zip customer
  2. Complete an order with an existing Zip account
  3. Ensure that Transaction data appears on Zip Dashboard
  4. Ensure the right items are used for item details
  5. Order ID returned in the POST /order API should be stored in the DB - this could be used to process refunds and for look-up
  6. Refund functionality has been implemented (recommended)
  7. ip Order Number should be included in the invoice if possible
  8. Idempotency-Key is included in the header parameters (recommended)
  9. Click and collect orders are implemented correctly, i.e pickup: true is specified in the order request (recommended)
  10. Handling of timeouts and connection errors (lack of response) on all API calls


  • Closed checkout
  • Cancelled order
  • Pressed “Back to Merchant” button


A professional looking integration/setup guide is recommended for channel partners

Professional means covering all areas in depth to a level where those integrating should not need to come to you with questions – it should be covered in the documentation

Final Certification


As part of the development process, you must have your site undergo certification

Certification Checklist

Here is the most recent version of our certification checklist that should be filled out prior to providing the Zip Integrations Team your testing/UAT environment links

NOTE: You should NOT go live or release your code to production until you have completed the above process and have received sign-off from the Zip Integrations Team

Certification Steps

  1. On completion of development – set aside a period of time to perform User Acceptance Testing (UAT)
  2. Work your way through the items outlined in the Certification Checklist, recording your actual results as you go. If any tests fail in a way that you believe is not acceptable, then perform necessary development work to fix the use case and then repeat the test until it passes
  3. Once you have completed and ticked-off all items in the checklist, add any additional notes in the checklist for the Zip team
  4. Forward the completed copy of this checklist through to Zip Integrations Team for review
  5. Provide the Zip Integrations Team with access to your UAT environment so that they may validate edge cases and well-known points of difficulty.
  6. When you and the Zip Integrations Team are happy that all tests have passed, you will be provided with sign-off and you will be able to go live or release your platform changes