Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation of PayTM Payment Gateway #6247

Closed
mrsaicharan1 opened this issue Jul 29, 2019 · 3 comments · Fixed by #6399
Closed

Implementation of PayTM Payment Gateway #6247

mrsaicharan1 opened this issue Jul 29, 2019 · 3 comments · Fixed by #6399

Comments

@mrsaicharan1
Copy link
Member

mrsaicharan1 commented Jul 29, 2019

Feature Description & Workflow
Integration of PayTM payment gateway is required to boost sales in India. The workflow would be in the following way

  1. When an order is placed, we generate the checksumhash on the server-side.
  2. to obtain the txn token, a call is to be made to the Initiate Transaction API with the checksum & parameters.
  3. We fetch the available Payment Options from the Fetch Payment Option API.
  4. User selects a payment option as Pay using PayTM
  5. User enters mobile number linked to PayTM. Calls Send OTP API & Validate OTP API.
  6. Call the Transaction Status API to verify the transaction response [essential]
  7. Redirect the user to the appropriate order page in accordance with the response
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label feature to this issue, with a confidence of 0.95. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@iamareebjamal
Copy link
Member

Please implement the endpoint in a way it is also usable on Android

@mrsaicharan1
Copy link
Member Author

Please implement the endpoint in a way it is also usable on Android

Yeah, will take care.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants