#aasdf-bnpl-connect

1 messages · Page 1 of 1 (latest)

small coralBOT
dense pawn
#

👋 @distant roost we help in real time here and we archive threads quickly as there are dozens of developers asking for help every day. It's sometimes best to work with our support team if you need to have a long running conversation at your own pace

#

If you have a clear question though I'm happy to try and help!

distant roost
#

OK, it was the BNPL issue with connected accounts. I had a meeting to jump into while waiting for a reply. Here is my original message:

Hello, we are implementing Buy Now Pay Later for all of our connected accounts. When testing out Affirm and Afterpay, we are being redirected to a Stripe Test payment page when we specify the on_behalf_of parameter. However, with Klarna it works as expected. If we do not specify the on_behalf_of parameter, we are able to access the Affirm and Afterpay sandboxes. Is this expected behaviour with connected accounts?

dense pawn
#

I don't really understand the question. It says "however it works as expected". What's the question? What works or doesn't work? what error do you get?

distant roost
#

It's in development, so using our testing key on Stripe... so working as expected means to redirect to the BNPL provider site to fill out on their sandbox page.

If I do not specify the connected account, when I do the confirm intent JS code (different function for each provider), it will redirect to the BNPL provider's sandbox site.

If I specify a connected account, only a payment intent for Klarna redirects to their site. Affirm and Afterpay will redirect to a stripe.com URL that has a button to confirm (approve? not sure the word here) the payment.

#

If you need some more concrete function names and URLs, I can provide them... please let me know

dense pawn
#

I'm really sorry I have no idea what any of this means. I still don't understand the problem

#

like are you getting an error? Right now you seem to indicate you do things and it just works, so what is the problem you have?

#

aasdf-bnpl-connect

distant roost
#

I'm seeing 2 different behaviours, only on Affirm and Afterpay, based on if i pass the on_behalf_of parameter to the intent or not.

I'm not sure if this is correct or not.

Examples:

  1. Create a payment intent with payment_method_types=["affirm"] and on_behalf_of=<connected account id>.

  2. Create a payment intent with payment_method_types=["affirm"] and no on_behalf_of paramater.

When I call stripe.confirmAffirmPayment() in the browser with JS it will do the following behaviour for each of the examples above.

  1. It will redirect to a stripe.com URL that says it is a test payment, and press a button to finalize it. I haven’t 't pressed the button, so I'm not sure what this page does.

  2. It will redirect to an affirm.com URL that does the BNPL applicatoin in Affirm's sandbox. When completed, it goes back to our site with a confirmed payment intent we can process.

dense pawn
#

Yeah Affirm is a bit weird and has a "sandbox" integration path that is annoying, I think this is new. Mostly you can ignore, it's all test mode so go through the steps as needed

distant roost
#

My questions are:

  1. Is this expected behaviour in both cases?
  2. Why is the destination redirection different?
  3. Why does Klarna's redirect always go to to the klarna.com for either of the examples (on_behalf_of exists, or does not exist)
#

So for Affirm, it sounds like #1 is answered... curious as to why we see different flows based on the parameters passed to the intent when it is created though (question 2).

dense pawn
#
  1. Yes
  2. I don't know
  3. Every payment method has different criteria and requirements
distant roost
#

OK, thank you. I'll go forward and pass this information on to our team that does the QA, so this is expected for Affirm and Afterpay.