FAQs

• What is paymentReference and is it mandatory in txnAttempt?

  Yes, paymentReference is a unique identifier to the payment Instrument sent in the getInstrument call and must be passed in txnAttempt.

• Will merchants have to collect CVV?

  Yes, CVV must be collected and passed in txnAttempt, ensuring PCI compliance.

• How long is paymentReference valid?

  It expires in 15 minutes. Merchants should call getInstrument again after expiry.

• Can merchants customize payment method UI?

  Yes, merchants can override the display information provided by Juspay.

• What all options can be shown with what all features are supported?

  In the default setup, the getInstrument call response will prioritize and return the user's last used, most used, and then saved payment instruments. This can be customized to return promoted instruments for new users or instruments based on the best available offers.

• What Payment options and features are not Supported?

  The Payment Widget does not currently support EMI transactions. The Payment Attempt feature is also not supported within the widget itself; however, it will function in the same way it currently does within the standard payment page flows.

• Can merchant exclude payment instruments with fluctuating success rates and prioritize more reliable options?

  Yes, merchant can either display these payment methods with a fluctuation message or prioritize the next best available option.