#gael_api

1 messages ¡ Page 1 of 1 (latest)

tawny lindenBOT
#

👋 Welcome to your new thread!

⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1212331670934655008

📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question. Thank you for your patience!

half spireBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

gilded bridge
#

hi! you don't need to/should not test in live mode really, you can just use test mode

#

but yeah I agree that in livemode it can be different because there are things like the bank app opening, and if you're using a mobile SDK integration that can cause some issues, but we don't have a good answer there

#

do you have more context on the problem you're facing?

opaque wharf
#

after bancontact validation. We have a return url to the the paygreen api (us). this page created a postMessage confirming payment or not. Except that intermediate popups break the reception of window.parent.postMessage in my opinion.

gilded bridge
#

fair enough! overall you should use webhooks to confirm the payment success, not Javascript on the frontend

#

the frontend could send requests to your backend in a loop to poll if the database has been updated yet

opaque wharf
#

Ok in this case I can delete the return url to our back from the paymentIntent?

gilded bridge
#

no, you still need the returnURL since that is where the customer will be sent after payment

#

but from your side the user visiting that page or a postMessage from that page doesn't mean they paid; they paid when you get a webhook on your backend server indicating the PaymentIntent succeeded

half spireBOT
opaque wharf
#

Ok thanks for the info