#devivo-checkout-email

1 messages · Page 1 of 1 (latest)

worn timberBOT
green panther
#

@echo vigil how can I help?

echo vigil
#

Hey! I'm building out a B2B platform and curious about what route I should be taking

#

In regards to Express or Standard or Custom. custom would be best for us long term but we're a small team and unfunded at the moment, ideally if we could change down the line without much friction (Start off as express or standard then "upgrade") that would be great but I just wanted to hash those kind of nuances out with a person versed in that before i started putting together more code and processes.

#

i see standard has no additional charges like how express has 2.00 per user a month, I guess that's because the user has to use stripe.com branding and dashboard, which initially is fine for us

green panther
#

Sorry for the delay! We're not experts on pricing here but I will say that it's not really possible to start with one connected account type and easily update to a different type. You'd have to re-onboard that business/individual and create a brand-new connected account for them

echo vigil
#

Yeah, Understood. Okay now my second question is about stripe checkout sessions

#

So i'm generating a checkout link via the API

#

But here's the confusing part-- See where it says "Email" , why is that under Shipping information?

If the user is buying a product and wants it shipped to a friend or family member (ie: flower delivery) but I want to use THEIR (the purchaser) email for the customer creation object, this UX is very confusinf or a customer

#

Because it makes you think the email it wants is the person you're shipping it too

#

So if someone wanting to buy something that's delivered to a friend, they would read "Shipping information" heading then see the "Email" below it , it will intuitvely make you think you'd put the friend's email there.. but then that friend would get the email about the transaction etc etc.

#

Are you seeing my predicament?

green panther
#

Could you share the Checkout Session ID?

worn timberBOT
#

devivo-checkout-email

echo vigil
#

it's on every single checkout I generate

#

So it's not specific to me or a checkout, I think it's just stripe's default UX flow for when you're also collecting shipping information/address

green panther
#

I'm not sure that's accurate. I have a test Checkout Session where 'Email' is not nested under Shipping information. If you have a request ID or Checkout Session ID handy, I'd like to see how the Session is being created and try to reproduce on my end.

echo vigil
#

okay cool bc every time i send this i get that flow

# 
const session = await stripe.checkout.sessions.create({
    line_items: lineItems,
    mode: 'payment',
    customer_creation: 'always',
    allow_promotion_codes: true,
    phone_number_collection: {
      enabled: true,
    },
    shipping_address_collection: {
      allowed_countries: ['US', 'CA'], // Add this line to specify allowed countries for shipping
    },
    custom_text: {
      shipping_address: { 
        message: `Please enter the recipient's delivery address:`,
      }
    },
    success_url: 'https://yourdomain.com/success?session_id={CHECKOUT_SESSION_ID}',
    cancel_url: 'https://yourdomain.com/cancel',
    // Note: You will need to handle shipping details separately for each order
    // if you are processing multiple orders with different shipping addresses.
  });
#

this is my command

#

here's a link just generated

#

id like the email to show up ABOVe the shipping information label

#

Or else its a little confusing

#

From what I understand, the email field is for the customer creation so i'd want the user placing the order's email there-- and shipping info can be a diff person so having it nested is misleading a bit

green panther
#

Ah, I see what you mean. Give me a few minutes

echo vigil
#

thanks , I appreciate it

green panther
#

Because it makes you think the email it wants is the person you're shipping it too

#

Agreed on the above. The email value provided in the Checkout Session will be used to create the Customer object on Stripe, so this is confusing.

#

I'll get this feedback over to our Checkout team

#

Looks like there's currently no way to shift this email field above/outside of the "Shipping information" header

echo vigil
#

yep there's no way to customize the text or anything either

#

I was going to try and just doing my own HTML checkout and seeing if i can collect addresses myself and pass them thruy to stripe

#

way more work but

#

For a florist , valentine's day coming up this would be huge sales avenue for us if we could get that UX working or i can just spin it up on my end

echo vigil
#

if even ever

#

is it possible to do it manually? using web elements or somethig?

#

Like my own Checkout form where i collect their email, addresses (shipoping/billing) then pass that to something that gets their card nfo securely through stripe?

#

Is that even possible ?

green panther
#

You could create your own form prior to redirecting your customer to the Checkout Session. The form could ask the customer to provide the recipient's email address (if applicable). That still wouldn't really fix any confusion caused by the "Shipping Information" heading in our Checkout form though

echo vigil
#

Ah so theres no way to not show that page?

#

paymentIntent or anything?

green panther
#

Oh, hold on. So you mean not use our Checkout product at all?

echo vigil
#

like we don't need the recpient's email at all, i only want the customer's email

#

yeah like until you guys fixed this verbiage

#

is there another approach I could do

green panther
#

It won't be a lightweight code change so I'd recommend against it

echo vigil
#

It'd me writing a full HTML form right and using paymentIntent ?

green panther
#

You could use the PaymentElement instead of Checkout but it's not exactly a plug and play swap

echo vigil
#

what would the flow be API wise

#

yah, i know it wont be a plug n play, but how does it work> Does the checkout get hosted by me? Is there a page before their card info goies in ?

green panther
echo vigil
#

ah yes ok

#

yah so i make my own checkout page basically

green panther
#

You'd create a page whre you'd display the PaymentElement instead of doing a full redirect to a Checkout URL

echo vigil
#

okay next question, for the payment element-- Do we get to generate that on the fly like i can for these checkout sessions (the code above)

#

here's an example of the flow im using so you can see how the platform works

green panther
#

Not exactly, no.

echo vigil
#

so id have to create a price and product?

green panther
#

No. If you integrate with the PaymentElement, you'd handle the creation of the PaymentIntent with your server code (this is something that Checkout currently handles for you so you never have to integrate with the PI APIs directly).

#

When you create a PaymentIntent, the result of the create call is a PaymentIntent that is in a "requires_payment_method" state. There's no link for you to redirect customers to a payment form for a specific PaymentIntent. You would have to use a PaymentIntent's client secret to render a PaymentElement client side

#

I recommend going through the custom flow quickstart guide to see this in action and then coming back to #dev-help when the channel is open if you have any other questions.

echo vigil
#

okay , and in the mean time i guess see if you can nudge that with the checkout team

#

ty:)