payment apps

Retired Boards Appdev Graphql Basics And Troubleshooting
1

The existing HPSDK handles payments/transactions in a pending state. With the upcoming payment apps only handling for rejections and resolves, how can fraud pending states be handled?

2

I have the same question. do you resolve it?

3

Hey @Fiyin

Thanks for raising this! Presently the Payment Apps API does not have the ability to handle that pending state. However, we acknowledge that this functionality would be useful and weā€™re working on building this at the moment. I canā€™t share an explicit ETA right now, but Iā€™d recommend to keep an eye on the Developer Changelog. Hope that at least explains things!

4

Thanks for your feedback. We confused if we want to complete the transaction integration in Septemberļ¼Œbefore the pending state readyļ¼Œhow should we process the pending stateļ¼Ÿ

5

Hey @Zsyk

Alas, there wouldnā€™t be a way to do that in the Payment Apps API at the moment, as the ā€˜pendingā€™ state does not exist as a concept in the GraphQL API. Naturally it exists on HPSDK presently. If migrating from HPSDK to the Payment Apps API, you have until December 31st 2021 as noted here.

The ā€˜pendingā€™ state on the Payment Apps API is a prioritised feature too, so itā€™s likely weā€™re going to be seeing it soon if that helps.

6

Got it, it looks we couldnā€™t finish integration until the ā€œpendingā€ feature ready. In fact we are the third-party payment provider, we know that the HPSDK deprecation date is December 31,2021. We just want to finish the whole integration process ASAP so that we have enough time to test payment and inform our merchant to migrate.

1 Like