Zooz: Hub Configurations

The following Zooz-related configurations are available from the Como Hub.

Button Actions

 

Button Action

Description

Pay with Online Service in Store

This action allows members to pay for their purchase using their app. After the member selects a credit card from the cards that they added to their app, the app displays a payment code. The member can give the code to the cashier in the store to complete the payment.

Pay with Online Service in App

This action allows members to pay for specific items directly in the app—such as catalog items, or club memberships. The member confirms or enters a custom payment amount, and selects a credit card from the cards that they added to their app. The payment is then processed.

Manage Credit Cards

This action allow members to manage their credit cards outside of a payment flow. Members can view, add or remove credit cards from this screen. For example, members can add credit cards to their app wallet in advance—so they’re ready to pay for items in the store.

 

Automations


Automations can be created based on whether or not the payment was successful or based on payment details—using the following triggers:

Trigger

Description

External payment succeeds

This trigger is based on a notification we receive from Zooz (IPN), and conditions can include shopping cart and purchase details. For example, you can register members that pay for their membership or send members gifts that they purchased in their app.

External payment rejected

This trigger is based on a notification we receive from Zooz (IPN), and conditions can include shopping cart and purchase details. A payment can be rejected because the payment failed. For example, you can notify a member that there was an issue processing their payment.

Pay with Como Wallet

This trigger is based on a successful payment (or PayWithBudget) API call.
Note: In very rare cases, it’s possible that the payment succeeded at POS, but Zooz notifies us later that the payment failed (External payment rejected).

Makes a purchase

This trigger can be used for in-app mobile payments, by adding a condition based on item code. This item code should be different than the item code used at the POS for the same item (to ensure that this automation isn’t triggered if a member purchases the item at the POS).


Settings

From Operation > Settings, you can configure settings related to Zooz.

 

Settings

Description

Payment Services

From External Services, you can specify your Zooz account credentials, the payment currency, and if the credentials you specified belong to your test account.

Payment Method

From Point/Credit Settings > Credit Card, you can specify how the POS should apply the Zooz payment to the purchase (for payments via the POS API). You can specify that it should be applied as a discount, a mean of payment or however the POS decides to apply it (Mean of payment/Discount). 

Note: Members can accumulate points (or get other rewards that depend on the purchase amount) only if the payment is applied as a mean of payment.

Quick Pay Wallet

From Point/Credit Settings > POS Payment Verification, you can specify if to use Zooz (Credit Card) for the Quick Pay feature. This allows members to pay at the POS using Zooz without a verification code when they identify with the temporary ID code from their app (appClientId).

Payment Verification Code Expiration

From Point/Credit Settings > POS Payment Verification, you can specify how long after the member generates a payment (verification) code from their app until this code expires. This is used for the in-store payment flows.

 

Filter Members

Search Filter

Description

Performed mobile payment

Search for members that performed a mobile payment with an external service (i.e. Zooz or PayPal). You can also refine your search according to amount, item code, branch ID and payment flow (in-app or in-store).

 

Updated
Was this article helpful?
0 out of 0 found this helpful