[Tarang]

I know you guys have used Stripe like experience to describe razorpay. We used to use Payzippy which was similar though had a few glaring differences.

I had a couple of questions as we need something like this.

Could you outline the differences due to the legal framework? Do you allow tokens/can customers save cards?, what about 3Dsecure? Can we use POST like api calls or do we use a very customisable iframe? Can you guys do pre-authorisations (such as when capture is false on the stripe api when you create a charge)?

[harshilmathur]

Payzippy was better but still was cumbersome to integrate, we have a much easier experience, you can checkout https://docs.razorpay.com for more info. - We do not support card tokenisation right now, it is in roadmap. - We do support 3D secure but handle it compeltely on our end, the merchant need not worry about handling it. - Right now, we provide iframe integration, but we will support POST calls very soon. Frankly, not many customers have asked for it. - We support Authorization and Capture Based payment but yeah pre-auths like those in US are not supported because of regulatory hurdles.

[captn3m0]

Formatted:

- Payzippy was better but still was cumbersome to integrate, we have a much easier experience, you can checkout https://docs.razorpay.com for more info.

- We do not support card tokenisation right now, it is in roadmap.

- We do support 3D secure but handle it compeltely on our end, the merchant need not worry about handling it.

- Right now, we provide iframe integration, but we will support POST calls very soon. Frankly, not many customers have asked for it.

- We support Authorization and Capture Based payment but yeah pre-auths like those in US are not supported because of regulatory hurdles.