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.

Sign up for GitHub

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

Jump to bottom

Implementing payments via tdlib #42

Closed
isopen opened this issue Feb 6, 2018 · 2 comments
Closed

Implementing payments via tdlib #42

isopen opened this issue Feb 6, 2018 · 2 comments

Comments

@isopen
Copy link
Contributor

isopen commented Feb 6, 2018 •
edited

This is a question for developers and managers.

I found several classes associated with payments.

getPaymentForm
getPaymentReceipt
messagePaymentSuccessful
messagePaymentSuccessfulBot
paymentForm
paymentReceipt
paymentResult
paymentsProviderStripe
sendPaymentForm

For example.
As processing your tdlib and server side.
There is provider0, provider1, provider2, provider3, etc.

  • Is the bot an provider?
  • Can you transfer payments to providers?
  • Can this replace the gateway for payments?
@levlam
Copy link
Contributor

levlam commented Feb 6, 2018

I can't understand what you are trying to achieve. You can try to find answers in description of the payments platform: https://core.telegram.org/bots/payments.

@isopen
Copy link
Contributor Author

isopen commented Feb 6, 2018 •
edited

Oppsss. This is the answer to all my questions. This is really cool a tool! Mega is cool! Thank you.

@isopen isopen closed this as completed Feb 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@isopen @levlam