In Order to use "Pay Later" Tender options like ZipPayZip Pay, it will first need to be setupconfigured.
Step-by-step guide
| BOTH the Store and the Customer must have a Zip Pay Account (The Store as a Merchant, the Customer as a Customer). |
 Configure the API Settings for Zip Pay in Striven
| If the Zip Pay Tender already exists in Striven - skip to Step 4. - From the Menu; choose System Manager - Till - Enter Tender Codes
- Create a New Tender for ZipPay Zip Pay (F5-New) that has a Payment Type of "Online Payment Gateway".
 Image AddedThe Description entered will show on Tender Reports - so make it something meaningful to the Store. - Save the New Tender Type (F9)
|
Image Removed Image Added |
- Press Enter to re-load the newly created ZipPay Tender on-screen
- Then either click the "Configure Gateway" button on the right of the Payment Type (above), ; or
- Click the "Gateway" Tab in the bottom-left corner of the Tender Type Codes form.
| Image Removed | Configure Gateway Settings for the Zip Pay API  Image Removed
Set
- "Ext Payment Type" MUST be set to Zip Pay to complete the final step.
 Image Added
|
 Image Added
| - From the menu; Go to POS - POS Settings.
 Image Added
- From POS Settings, go to the POS Settings Tab on the RHS.
 Image Added
- Under the "Payment Gateway Station" group in the Bottom LHS, select the ZipPay Tender Code and click the Register Button
 Image Added
NOTE: If the ZipPay Tender Code does not appear in the grid; go back to Step 3 and ensure that "Ext Payment Type" is set to Zip Pay in the ZipPay tender. When prompted; - "Store/Location ID" is given to the Store to represent each individual terminal connecting to Zip Pay from this Store Location (found on the Merchant Dashboard).
- "Merchant ID" can be found on the Settings/Integration Details Page on the Zip Pay Merchant Dashboard.
Go to:  Image Removed
| Image Removed |  Image Removed
|
(The Zip Pay Merchant Account must have Admin Access to have access to the Integration Settings) Image Added
NOTE: If the Integration Details sub-menu item does not appear, the store does not have Admin access. You will need to contact Zip Pay to get this information. |
Image Added |
|
 Image Added
|
|
 Image Added
|
|
 Image Added
|
|
| Notes: | The Zip API credentials for the merchant must be able to be configured in your Point of Sale |
system. This may be done within the POS, within a server that the POS connects to (especially if |
cloud hosted), within the Windows registry of the POS, or may be configured in the terminal and |
pushed to the POS from there.
The parameters that need to be configured (at a minimum) for each POS to work are:
1. API URL (either the sandbox or production URL)
2. API Key (a key provided by Zip, representing the merchant account)
3. Location ID (an identifier provided by Zip for each store or branch)
4. Device ID (an identifier representing the individual POS system that is being configured)
Purchase Transaction
Purchase using Zip (Direct POS) |
This flow may not exactly reflect the way in which you would implement the flow,
however the idea is to provide a general guideline on this use case. Please discuss
your method of implementation with your sales engineer so that we may update this
proposal with your actual flows, to allow for better technical support after go live.
After having registered a consumer account on Zip the customer will ask the operator to make a |
payment with Zip. The operator will, having already scanned all products on the register, select |
the relevant Zip tender type on the POS system. | Image Removed | Image Removed | Image Removed |
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@a51 |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label in ( "zippay" , "tender" ) and type = "page" and space = "SD" |
|---|
| labels | Zippay Tender |
|---|
|
...
