#tiffany-defaultPM

1 messages · Page 1 of 1 (latest)

static swallowBOT
shell ginkgo
#

Hello! Can you share an example Customer ID that's unexpetedly getting the default payment set so I can take a closer look?

static swallowBOT
#

tiffany-defaultPM

devout canopy
#

This is applying to every customer we have (our company's Account ID:
acct_1ECrNaG0kXZ7QBQW)

#

Here's one of our test customers: cus_PMZk2MhZkvx5FH

shell ginkgo
#

Taking a look now!

#

Hmmm... I'm surprised this is happening - it looks like the hosted invoice page is autoamtically setting it as the default on the customer for some reason. Let me see if I can reproduce the behavior and maybe pull in some other folks to also take a look

devout canopy
#

Thank you!

shell ginkgo
#

Okay I'm able to reproduce - just checking with some other folks to see when this started happening

shell ginkgo
#

So we did some digging - I believe this general behavior (of setting a default PM on the customer) has been in place on the Hosted Invoice Page for a while and there isn't really a way to disable it. The behavior changed slightly when we updated our Hosted Invoice Page to create Sources instead of Payment Methods, but even when we were using Sources the Hosted Invoice Page would create a Source and if it was the first Source it would automatically be set as the default

static swallowBOT
devout canopy
#

Ah so, even if we update to the newest API version, nothing would change?

shell ginkgo
#

Correct, nothing about the behavior would change

devout canopy
#

I see, another question I had was is that why for the Add Payment Method flow in the UX portal, we are not able to enable a checkbox for "Add Payment as Default Payment?

#

We have seen this capability before with Stripe, but cannot figure out how to add it for our account

woeful thicket
#

HI 👋
I'm stepping in for my colleague who has to go

#

When you say the "UX portal" are you referring to the Hosted Invoice Page or the Customer Portal?

devout canopy
#

Customer Portal I believe, when a customer goes to Add a Payment Method

woeful thicket
#

Do you have an example Portal Session ID where this feature is not present?

#

Are you creating this sessions via the API or the Dashboard?

devout canopy
#

via the API

woeful thicket
#

Okay. Do you have a billing portal configuration object you are using when you create the sessions?

devout canopy
#

Actually sorry, I think it's configured via the Dashboard

#

We have not turned this live yet, it is only in our test environment

woeful thicket
#

That's okay. Do you have an example Session ID I could review?

devout canopy
#

test_YWNjdF8xRUNyTmFHMGtYWjdRQlFXLF9QVVI2OFpycVBaRGR0bHlhZGt5RUhGR0JaeUhKNjBP0100BtioSptx

woeful thicket
#

Thank you, I'm taking a look now

#

Hmmm....it's saying that isn't a valid object

#

A customer portal session will start with bps_

devout canopy
#

tagging my co-worker @warm escarp to take a look

warm escarp
#

Found it : bps_1OfSDtG0kXZ7QBQWOgvOOPtY

static swallowBOT
split prairie
#

Hi taking over here

#

And catching up on context

#

Just for clarification, are you saying you used to see a set as default checkbox in the customer portal?

#

But now it dissappeared?

warm escarp
#

Hi @split prairie we haven't used the customer portal on this account yet. We have another account where we are using the portal and this checkbox is visible.

split prairie
#

I see gotcha

#

Looking

warm escarp
#

The other account is using the API for billing portal, this new account's test mode is using the dashboard/no code. Other than that I'm not seeing material differences between the two.

split prairie
#

Do you have the other account's id where you are seeing the checkbox?

#

Can you share that other account's id

warm escarp
#

acct_1FbFs5JrbjwvGEol is the other account

split prairie
#

Thanks

#

Looks like we only surface that checkbox if the customer already has a default PM/source. If there’s no default PM and they’re adding their first PM through the customer portal then it’s always set as the default.

warm escarp
#

Thanks for the clarification! @devout canopy is this what we needed?

devout canopy
#

Yes I think so! Thank you all!