Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Vineeth 14 posts 134 karma points
    Jan 31, 2019 @ 10:11
    Vineeth
    0

    How to handle QuickPay10 ProcessCallback locally

    How can we handle QuickPay10 ProcessCallback on Local? The transaction has been done on the Quickpay and status is showing authorize in Quickpay dashboard of payments. But the payment state is not being updated in Teacommerce order's status.Still showing intialized as status in the teacommerce backend and callbackUrl doest work because of it localhost url.

    Is there anyway to debug the and handle the call back url on local machine ?

    And one more doubt is Teacommerce will handle automatically the callback and updates the order status and payment state ?

  • Matt Brailsford 2067 posts 10159 karma points MVP 5x c-trib
    Jan 31, 2019 @ 11:20
    Matt Brailsford
    100

    Hi Vineeth,

    To test webhooks locally, we use a tool called ngrok https://ngrok.com/ this allows you to create a temporary URL that tunnels through to your localhost machine. With this, you can configure a public URL for your local site and then use that URL to test the webhook.

    As long as the webhook succeeds, it should update the payment accordingly.

    Hope this helps

    Matt

  • Vineeth 14 posts 134 karma points
    Jan 31, 2019 @ 11:54
    Vineeth
    0

    Yeah make sense, But https://ngrok.com/ is not working for me. But I will try anyother alternative for ngrok.

    Actually we are going to use a custom payment form instead of QuickPay payment form. What all should we need to handle after that? Any advice to implement this? :)

    Thanks

  • Matt Brailsford 2067 posts 10159 karma points MVP 5x c-trib
    Jan 31, 2019 @ 12:08
    Matt Brailsford
    1

    Now that's a different question :)

    I'd suggest you take a look at the payment provider on GitHub here:

    https://github.com/TeaCommerce/Payment-Providers

    The simplest one would be the invoice one, which this just passes orders through, but then I'd look at things like the PayPal one for more complex ones.

    Generally you need to define some settings, create a method to generate the payment form, and have a callback handler method to handle a callback from the payment provider and to then mark the transaction as complete.

    There is more you can implement like refunding payments, canceling etc, and listening for webhooks, but those aren't essential. I'd say start simple, then add the extra features when the simple one works.

    Hope that helps

    Matt

  • Vineeth 14 posts 134 karma points
    Jan 31, 2019 @ 12:22
    Vineeth
    0

    Yeah definitely .Thanks for the help :)

Please Sign in or register to post replies

Write your reply to:

Draft