Payment Methods

Merchant ID provided by Juspay

We recommend passing the customer_id as the x-routing-id. If the customer is checking out as a guest, you can pass an alternative ID that helps track the payment session lifecycle. For example, this could be an Order ID or Cart ID.

Merchant Id for which you need to fetch the available payment methods

Pass true to fetch payment methods that support EMANDATE transaction

Pass true to fetch the payment methods that support direct debit transactoin

Pass true to fetch supported gateway_reference_id against payment methods
Use this parameter only if you have a use case of Gateway Reference Id. Click here to read more

Pass true to fetch payment methods that support Third party validation (TPV) transaction

Pass true to fetch applicable outages on payment methods.
Each payment method object has a key juspay_bank_code. By using juspay_bank_code as a lookup in the outage array, you can determine whether the payment method has outage or not.

NOTE: The outage basically functions based on a score at each payment method level. We maintain this score from for all Merchant- Payment method combinations. For each transaction created, we penalise this score by a small amount and if the transaction is successful (CHARGED or AUTHORIZED), then we add to this score so as to reward the Merchant <> Payment method.

We have 2 outage statuses: FLUCTUATE and DOWN and we assign these once the score falls below a certain threshold at our end. There is a soft reset from time to time to check the health where we allow a few transactions to go through, based on which we decide whether the Merchant <> Payment method combination is back UP (no outage being faced).

Apart from this, we reset the overall score at a pre-defined interval as well.
These thresholds can be customised based on merchant requirements.