nyxi_automatic-payment-methods | Stripe Developers | Page 1

wispy tangleBOT May 28, 2024, 12:43 PM

#

proper minnowBOT May 28, 2024, 12:43 PM

#

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.

nyxi_docs, 3 days ago, 11 messages
nyxi_pi-autopms, 4 days ago, 62 messages
nyxi_invoice-return-url, 4 days ago, 79 messages

wispy tangleBOT May 28, 2024, 12:43 PM

#

👋 Welcome to your new thread!

⏲️ 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.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 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/1244994481288249407

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

deft tree May 28, 2024, 12:48 PM

#

Hi there 👋 we automatically show all Payment Method types that match the criteria of the intent being used. It looks like the intent you created used a presentment currency of dkk, which isn't supported by most of the Payment Method types you mentioned. The only one mentioned that seems to match the currency is MobilePay.

wispy tangleBOT May 28, 2024, 12:49 PM

#

nyxi_automatic-payment-methods

sage flicker May 28, 2024, 12:49 PM

#

deft tree Hi there 👋 we automatically show all Payment Method types that match the criter...

Yes, so why no MobilePay?

deft tree May 28, 2024, 12:49 PM

#

I'm still looking into that

sage flicker May 28, 2024, 12:49 PM

#

ok

deft tree May 28, 2024, 12:51 PM

#

Checking with teammates where the perfect tool for looking into this got moved to

sage flicker May 28, 2024, 12:52 PM

#

Alright

#

maybe I need to provide return_url when creating the intent to make the elements support redirect-based payment methods?

#

(Which MobilePay is)

#

But docs say "only when confirm=true" which we dont

#

I guess that's what https://docs.stripe.com/api/payment_intents/create#create_payment_intent-automatic_payment_methods-allow_redirects solves

deft tree May 28, 2024, 1:01 PM

#

This looks like a charge for one of your Connected Accounts, and MobilePay seems to off by default for your Connected Accounts.
https://dashboard.stripe.com/test/settings/payment_methods/connected_accounts

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

sage flicker May 28, 2024, 1:01 PM

#

aha, ok

deft tree May 28, 2024, 1:01 PM

#

And that Connected Accounts seems to be inheriting defaults.

sage flicker May 28, 2024, 1:01 PM

#

Ok I'll enable it now

#

I had enabled it on the connected account itself

#

It works now, but for Google Pay and MobilePay: Is there are way to remove this huge block of "You will be redirected" text? Would prefer it just checked the row and didn't expand at all.

#

#

(coloring/styling is WIP here)

deft tree May 28, 2024, 1:09 PM

#

No, but I'll capture your feedback that this is something you'd be interested in having more control over in the future.

sage flicker May 28, 2024, 1:10 PM

#

Yes please, I think this looks fairly bad to be honest

#

We had a custom payment selector before which was basically this, but with no row expansion if you don't need to provide info (like card)

#

#

Do you know how to change the color of the white block in the screenshot above? We're having a bit of trouble targeting it with the styling guide.

#

deft tree May 28, 2024, 1:19 PM

#

Hm, not offhand. I know the Appearance API is the right approach if that is adjustable, but I'm not sure what the exact variable within it for those are.

sage flicker May 28, 2024, 1:21 PM

#

Brute force then I guess

#

Something you could consider creating was a "config creator" where you can select each item and pick the color/whatever for it, then generate a config object. Would be very helpful.

#

I guess the inspect tool does 90% of that. We'll try.

deft tree May 28, 2024, 1:24 PM

#

That's exactly what I was firing up to look for clues

sage flicker May 28, 2024, 1:25 PM

#

The inner-most object here is classed as Block

#

but it ignores anything we give it and overrides it with a var() that contains a stripe elements variable

#

Tried with color as well to change text color, no dice

deft tree May 28, 2024, 1:30 PM

#

Looking at the samples at the top of the page (https://docs.stripe.com/elements/appearance-api) and how they render, I do think .Block is the right path to go down.

#

What do you have right now for your appearance options?

sage flicker May 28, 2024, 1:31 PM

#

I think we solved it by applying the variables first (step 2, after theme). We may not need to go into the rules at all.

#

It seems it applies colorBackground to the block

#

I think my guy just skipped a step 😄

deft tree May 28, 2024, 1:32 PM

#

Glad you were able to get it sorted!

sage flicker May 28, 2024, 1:45 PM

#

Hmm yea it's still playing games with us. Like it will color all input fields correctly (using .Input), but the email input for link login remains white

#

and looking at the inspector, it has .Input as its class

#

but it also has p-EmailField

deft tree May 28, 2024, 1:49 PM

#

You're now talking about the section that appears when you click on the "something 1-click something" line that brings up Link?

sage flicker May 28, 2024, 1:50 PM

#

yes

#

All other input fields are dark as expected

#

but email field is white. We can change it by styling the private selector, but the guide says that's a nono

deft tree May 28, 2024, 1:53 PM

#

Hm, my suspicion is that one is broken.

sage flicker May 28, 2024, 1:56 PM

#

That's unfortunate

deft tree May 28, 2024, 2:01 PM

#

Sorry, I'm trying to test it out and confirm, but it's slow going.

sage flicker May 28, 2024, 2:03 PM

#

Yeah no problem. Another thing. Since we're now moving to completely async handling (confirm on frontend, wait for webhook), is there a good way to provide an email that does not trigger the receipt email from Stripe?

#

Need to send an actual receipt for the product to the customer, but with this approach and in this case, we don't have any endpoints for data collection

#

Its like a single page with "prepay for your reservation" where the amount, product etc. is already set up

#

I can of course just make an endpoint for it, but would be nice to just do it all in one go

deft tree May 28, 2024, 2:05 PM

#

metadata is what comes to mind
https://docs.stripe.com/metadata
though it feels a little odd to store an email address there. Are you creating and using Customer objects as part of your flow?

Metadata

Learn how to use metadata to save additional information.

sage flicker May 28, 2024, 2:06 PM

#

deft tree `metadata` is what comes to mind https://docs.stripe.com/metadata though it feel...

No customer, no

deft tree May 28, 2024, 2:09 PM

#

I think metadata is the best fit then.

sage flicker May 28, 2024, 2:10 PM

#

I can update the metadata on the client using the intent secret?

deft tree May 28, 2024, 2:13 PM

#

I don't believe so.

sage flicker May 28, 2024, 2:14 PM

#

Frontend collects the email

#

So I guess there's no way to do that then

#

We'll solve it with a dedicted endpoint then

#

I have some more questions though:

If the payment intent is paid for after its amount was changed from another source, what happens? Does the client secret change and make it not work?

#

How do we return the payment intent to "requires_payment_method" without actually giving it a payment method? but without canceling the intent

#

2 being if the webhook comes in and the amount was wrong because of 1. above

#

Webhook does capture, so it would just not capture it if the amount was wrong

deft tree May 28, 2024, 2:16 PM

#

The only other place I can think of, but I'm not certain if it triggers automatic emails, is to provide it in payment_method_data.billing_details.email
https://docs.stripe.com/js/payment_intents/confirm_payment#confirm_payment_intent-options-confirmParams-payment_method_data-billing_details

Stripe JS Reference

sage flicker May 28, 2024, 2:16 PM

#

deft tree The only other place I can think of, but I'm not certain if it triggers automati...

Good call, will try

deft tree May 28, 2024, 2:17 PM

#

sage flicker I have some more questions though: 1. If the payment intent is paid for after i...

What do you mean, like chanigng the amount of the intent after it has succeeded? Did you try in your testing, where I'd expect the request to error?

deft tree May 28, 2024, 2:17 PM

#

sage flicker 2. How do we return the payment intent to "requires_payment_method" without actu...

From what state?

sage flicker May 28, 2024, 2:18 PM

#

deft tree What do you mean, like chanigng the amount of the intent after it has succeeded?...

I did not try yet, no. But imagine:

Amount is set
Customer loads payment page and fetches the intent
Amount is changed from different source
Customer completes/confirms the payment intent

sage flicker May 28, 2024, 2:18 PM

#

deft tree From what state?

from requires_capture

deft tree May 28, 2024, 2:18 PM

#

Hard to say without more context about how you built your integration. A deferred intents flow will throw an error at confirmation, I believe, due to the amount mismatch.

sage flicker May 28, 2024, 2:19 PM

#

So I basically will never have to worry about the amount on a requires_capture intent being wrong, because it won't be possible to confirm it with the wrong amount?

deft tree May 28, 2024, 2:20 PM

#

Depends on your flow, try it out

sage flicker May 28, 2024, 2:21 PM

#

Assuming you update the amount from a different source; if the modification goes through, the payment cannot be confirmed later with the wrong amount.

#

I guess I'll try

#

This, probably: https://docs.stripe.com/error-codes#payment-intent-amount-reconfirmation-required

deft tree May 28, 2024, 2:22 PM

#

If you're using an intent-first flow, I don't think that same protection is in place, because the intent is the source of truth.

sage flicker May 28, 2024, 2:23 PM

#

deft tree If you're using an intent-first flow, I don't think that same protection is in p...

Yes, so:

Create PI, set amount (set SoT, backend)
Load payment intent from Stripe (load SoT, frontend)
Modify payment intent (new SoT, backend)
Attempt to confirm out-dated payment amount (frontend)

#

They're all looking at the intent

#

I shall confirm

deft tree May 28, 2024, 2:28 PM

#

Yeah, I think that will let the payment be confirmed offhand.

sage flicker May 28, 2024, 2:28 PM

#

I think it will throw https://docs.stripe.com/error-codes#payment-intent-amount-reconfirmation-required

#

but let's see

#

Possibly when trying to do the capture

wispy tangleBOT May 28, 2024, 3:45 PM

#

#nyxi_automatic-payment-methods