#simbaclaws
1 messages ยท Page 1 of 1 (latest)
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.
- simba-embeddedcheckout-tracking, 20 hours ago, 79 messages
wow, I'm blind, it's payment_method_configuration
๐ yup you beat me to it
hmmm odd it's still only displaying credit card
I'm using a subscription inside of the checkout form
If you give me a specific Checkout Session ID I can take a close look
hold on, let me log a checkout id then
brb
isn't the checkout session ID from doing an actual checkout from the return url?
I haven't tested that yet, but I'll give it a try
by the way, why does the Card information check for card validity when I have it set to test mode?
You should be getting a Checkout Session ID back as soon as you create the Checkout Session in the API
For card validitity we do some basic checks in the UI (we expect cards to pass the Luhn check that determines whether a card is valid or not)
isn't that the client_secret?
when I do the payment I'm getting a Payment Required by the way... Also I'm running this on a dev server on localhost without https, and I see a console log about apple ot google pay that I must serve it over https
If you're getting back an ID like cs_test_123 that would be the checkout session ID
hmmm so the checkout session creates an ID as well...
{
id: 'cs_test_a1nshO7ppGmQd2IUgNpNh2WWIcn3fhMNfJZAdEEhKLMlbUbVR0TxQMqg6Y',
object: 'checkout.session',
after_expiration: null,
allow_promotion_codes: null,
amount_subtotal: 999,
amount_total: 999,
automatic_tax: { enabled: false, status: null },
billing_address_collection: null,
cancel_url: null,
client_reference_id: null,
client_secret: 'cs_test_a1nshO7ppGmQd2IUgNpNh2WWIcn3fhMNfJZAdEEhKLMlbUbVR0TxQMqg6Y_secret_fidwbEhqYWAnPydgxxxxxxxxxxxxxxxxxx',
consent: null,
consent_collection: null,
created: 1705606098,
currency: 'eur',
currency_conversion: null,
custom_fields: [],
custom_text: {
after_submit: null,
shipping_address: null,
submit: null,
terms_of_service_acceptance: null
},
customer: null,
customer_creation: 'always',
customer_details: null,
customer_email: null,
expires_at: 1705692497,
invoice: null,
invoice_creation: null,
livemode: false,
locale: null,
metadata: {},
mode: 'subscription',
payment_intent: null,
payment_link: null,
payment_method_collection: 'always',
payment_method_configuration_details: { id: 'pmc_1OZqNsE2vn5fxmgK0ufrqC3k', parent: null },
payment_method_options: null,
payment_method_types: [ 'card', 'link' ],
payment_status: 'unpaid',
phone_number_collection: { enabled: false },
recovered_from: null,
redirect_on_completion: 'always',
return_url: 'http://localhost:3000/?session_id={CHECKOUT_SESSION_ID}',
setup_intent: null,
shipping_address_collection: null,
shipping_cost: null,
shipping_details: null,
shipping_options: [],
status: 'open',
submit_type: null,
subscription: null,
success_url: null,
total_details: { amount_discount: 0, amount_shipping: 0, amount_tax: 0 },
ui_mode: 'embedded',
url: null
}
this is what payment method types says:
payment_method_types: [ 'card', 'link' ],
which is wrong, because it should fetch it from the payment_method_configuration_details
What payment method types are you expecting instead of card and link?
Cards, Cartes Bancaires, Apple Pay, Google Pay, Link, BLIK, Bancontact, EPS, giropay, iDEAL,
those are the ones that are enabled with the profile id
or config id rather
oh wait, not cartes bancaires
When you use payment_method_configuration we still do some filtering to determine which of the PM types will actually work for the payment. In this case, eps, giropay, blik aren't showing up because they don't support setup_future_usage / subscriptions
GIve me a few more minutes to look into ideal and bancontact
what about google and apple pay?
ah google pay requires registration of trusted domains
google and apple pay are not separate payment method types - they'll show up in supported browsers if card is enabled
they're not showing up for me, but I also have a console log saying: ] If you are testing Apple Pay or Google Pay, you must serve this page over HTTPS as it will not work over HTTP. Please read https://stripe.com/docs/stripe-js/elements/payment-request-button#html-js-prerequisites for more details.
that's probably why
Ah I forgot you were doing embedded
si
Yeah you'ld need to get the domain registered for apple/google pay to work then
how about the other payment methods you mentioned? iDeal and Bancontact?
still looking into that - give me a bit
sure thing, take your time
I find it weird that it responds with only link and card when I have a config setup though
For bancontact and ideal I believe it's because they don't support subscriptions natively
You don't have paypal enabled in that payment method configured though
oh you're right!
I didn't notice that
it also requires a trusted domain I see
so in any way, if I want to do subscriptions, I could only use: payla, google pay, apple pay, or credit card right?
paypal
and I need to for apple pay, google pay and paypal to setup the domain and ssl
Hi there ๐ jumping in as my teammate needed to step away. Catching up real quick.
I will absolutely be sure to pass that on!
Think I'm caught up, and yes, you will need to host your test site over HTTPS and register the domain to fully test wallet payment methods. Additionally for those, Stripe typically requires that you already have a card saved in the associated wallet (Google Pay/Apple Pay) before we will display the button. So if you don't already have cards in your wallets that could also contribute to why you aren't seeing those options.
ah, that makes sense, thank you
Do I have to connect my google wallet and google payu to stripe somhow? I'm having a hard time neavigating stripe for the correct info
No
you just said I needed to get a card saved in the associated wallet, what did you mean by that exactly?
That means you need to have a card in your Google Pay or Apple Pay wallet
You won't find Stripe guides on how to use the wallets provided by Apple and Google, you'll likely need to consult their documentation for guidance on how to properly set those up.
So in order for me to view google pay I need to have CARDS in my google pay already?
so, let me get this straight, I need to be signed in to google in my browser, and have a wallet connected to my google pay, in order to see the button?
Yup
I'm a bit confused on how the website would know it's logged in to google
I'm pretty sure it's built on top of the Payment Request API, which the browsers have support for:
https://developer.mozilla.org/en-US/docs/Web/API/Payment_Request_API
aha
ok, yeah that could make sense
so if I'm on firefox, this shouldn't work? since the payment request api isn['t supported in firefox?
or does stripe have libraries for bcompatibillity of some sort if the payment request api is not available?
same counts for webview android
what if I'm not logged in to google, can I still see the google pay button?
hmmm ok
Are you seeing the button while not being logged in?
and android mobile too?
no I'm not seeing the button in either case
but that's probably because I'm not rendering the site on https, but running it on localhost
ah chrome for android has suport
Yup, I'm pretty sure it isn't expected to work in Android's webviews, and if you aren't serving over HTTPS that'll also cause problems
I'm just trying to get it setup and working locally before I launch the product
but that probably doesn't work
so I'll try creating a test domain to see if I cn accept payments, so I can develop on a test server
I need to save some info in a database somewhere so that the aplication I'm developing knows that a logged in user has an active subscription
or is there also an api request from stripe for that?>
sorry I'm a bit new to stripe
Sounds like you may be looking for webhook endpoints, if you want the data to be pushed to you:
https://stripe.com/docs/webhooks
this guide is more specific to Subscriptions
https://stripe.com/docs/billing/subscriptions/webhooks
Or if you're following our guide for using Checkout Sessions to create Subscriptions, this is the step where we start talking about receiving and handling Events that we can push to webhook endpoints that you create:
https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=stripe-hosted#provision-and-monitor
hmmmm
I'm using a embedded form though, it doesn't show information about handling events when using the embedded form
oh nevermind
it's step 4
privision access
am I missing something or is there no explenation for creating the webhooks on the embedded form example?
I'm going to be creating a customer portal
as well as want to respond to webhooks
Nope, you're right, it doesn't go into registering the webhook endpoint within Stripe., that's covered in the first guide I linked. This section specifically for registering it with Stripe:
https://stripe.com/docs/webhooks#register-webhook
This section for the key detail that needs to be in your response (which is the status code that you send with the response):
https://stripe.com/docs/webhooks#webhook-endpoint-def
alright, I'll have a look there, thank you so much โค๏ธ