Qwikcilver Documentation

Gift cards feature allows merchants to enhance user engagement by integrating gifting experience including corporate gifts, personal gifts and personalised offers from merchants.

Key Features :

1. Check Gift card balance. 

2. Allows the customer to pay the entire order with a single gift card.  

3. Allows the customer to pay with multiple gift cards 

4. Allows customer to pay with 1 traditional instrument (NB, Cards, Wallets , UPI) and multiple gift cards.

1. Gateway Configuration

Gateway Configurations

Step 1: Dashboard

Sandbox Dashboard Url - https://sandbox.portal.juspay.in

Production Dashboard Url - https://portal.juspay.in/

Post Login to Dashboard, Click on EC Operations > PG Control Centre. From the Other Gateway

• Select Qwikcilver Gateway

• Please enter the below credentials obtained from Qwikcilver Team.

Scroll inside to view more

Juspay Dashboard Fields	Mandatory / Optional	Remarks
Terminal ID	Mandatory
Merchant Outlet name	Mandatory
User Name	Mandatory
Password	Mandatory
Forwarding entity Id	Mandatory
Forwarding entity password	Mandatory
Host tag	Mandatory	Should be configured without the “http://”
Rest of the fields	NA

Expand

3 columns 9 rows

Payment Method Configuration

Select QWIKCILVER Gift Cards from payment Method Configurations

2. End-to-end User flow

Only Gift Card

User lands on the Juspay Hosted payment page and clicks on the Add Gift card option.

Post entering the correct details, user would be able to add the card and make payment.

In this case, Juspay will call Direct debit to QC and the whole amount would be in debited from the users card.

Attaching Sample Flow

Split Payment Flow

In case user does not have sufficient balance in the gift card, User can choose to make the remaning amount payment via another Gift card, Debit/Credit Card, UPI or NB.

Juspay will initiate transaction call to the other payment method and will simultaneously call PreAuth to QC. Once Juspay gets a successful confirmation from the other payment method, Juspay will call capture to QC.

Else, cases where primary txns fails, juspay will call void to QC.

Attaching Sample Flow

3. Sample Requests and Responses

With your existing implementation with Juspay, transaction details such as payment method , txn_id and other details are present in the root structure of the orderStatus JSON block.

However, With the integration with Qwikcilver, which involves split transactions, you will find a txn_list as an array block containing the two transactions (UPI + Qwikcilver). It is essential to extract parameters from within the txn_list array block. A sample response is attached below for reference.

Order Status

Request

Order status request

Response

Order status Responses. (Kindly use the drop down below)

1. Only Gift Card

2. Gift Card + Cards

3. Gift Card + UPI

4. Two Gift cards + UPI

5. Gift card + UPI Mandates

Refund Calls

1. Refund requests (full/partial) can be initiated by a Juspay’s merchant at Transaction level.

2. Given that Qwikcilver transactions are always split between an existing Gateway and Qwikcilver Gift Cards.

3. For Transaction based refunds

   A. Merchant would initiate refunds against all transaction Ids, with transaction Id and amount to Juspay

   B. Merchant will ensure the amount checks and the refund split for both full and partial refunds.

   C. Juspay’s refund response will remain the same as what merchants currently see for transaction based refunds. No additional handling required.

Request

Response

4. Webhooks:

As the orderStatus Structure also changes, the webhook would also change. Attaching a sample response for the same.

4. Testing Scenarios

For the final step towards completing your Qwikcilver Integration, Kindly perform the below mentioned test cases

Note: These test cases as part of Basic test cases, Juspay recommends merchants to do extensive testing for all available payments methods available for your MID.

5. Limitations

1. Juspay is not supporting Offers on traditional instruments if Gift card is added

2. Refund is to be done at a txn level and not at order level. If full amount has to be refunded, Transaction ID based refund API (attached above) to be hit twice with TxnID for each.

6. FAQ’s