sayori_api

[spice plaza]

👋 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/1398150549131624542

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

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.

• sayori_best-practices, 4 hours ago, 7 messages
• sayori_unexpected, 1 day ago, 9 messages

[soft mesa]

i recognize that one workaround is to tie the metadata to the product_data instead, then fetch more data (expanded) than the webhook naturally provides. but then it makes me wonder where the metadata on the line items is going, and potentially means i can get away with not expanding product

[spice plaza]

⛔️ Stripe developers have stepped away for a short while

Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.

[misty phoenix]

• If you pass in  metadata [0], the Checkout Session object will contain the metadata.
• If you pass the metadata into subscription_data.metadata [1] (this is for mode="subscription") - the Subscription will contain that metadata [2], and so will the Invoice [3] and Invoice Line Items [4]
   
  You could pass in the same  details to metadata and subscription_data.metadata when creating the Checkout Session.

You can also read up more on metadata in more detail here : https://docs.stripe.com/metadata

[0]https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-metadata
[1] https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-subscription_data-metadata 
[2] https://docs.stripe.com/api/subscriptions/object#subscription_object-metadata 
[3] https://docs.stripe.com/api/invoices/object#invoice_object-subscription_details-metadata
[4] https://stripe.com/docs/api/invoices/line_item#invoice_line_item_object-metadata

[soft mesa]

hmmm.... as part of https://dashboard.stripe.com/logs/req_MAdtE2CO825nj0, I put the metadata into line_items

[misty phoenix]

from what I'm seeing, you put it into the Checkout Session

[soft mesa]

but I don't see this metadata when fetching the invoice

okay, so the metadata as part of the line_items doesn't go anywhere else? because I can see that if I stick the metadata into line_items.price_data.product_data then it does get transferred all the way to product

[misty phoenix]

let's take a step back.The metadata was not defined in line items in req_MAdtE2CO825nj0

{
  billing_address_collection: "required",
  cancel_url: "https://....com/api_key",
  client_reference_id: 
"3055978842"
,
  currency: "usd",
  customer: "cus_.",
  customer_update: {
    address: "auto",
    name: "auto",
  },
  invoice_creation: {
    enabled: "True",
  },
  line_items: {
    0: {
      metadata: {
        test: "2",
      },
      price_data: {
        currency: "usd",
        product_data: {
          description: "100,000 points",
          name: "Poe Add-On Points",
        },
        unit_amount: "0",
      },
      quantity: "1",
    },
  },
  metadata: {
    amount_points: "1000000",
    price_country_code: "US",
  },
  mode: "payment",
  success_url: "https://....com/api_key?purchased=true",
  tax_id_collection: {
    enabled: "True",
  },
}

^ you defined the metadata in the Checkout Session

[soft mesa]

    0: {
      metadata: {
        test: "2",
      },

is the metadata i'm talking about

[misty phoenix]

ah, i see, sorry, totally missed that out

[soft mesa]

i do recognize this is a beta feature too

[misty phoenix]

gimme a while to see what I can find

hmmm, okay I can't really find a lot of details on this beta at the moment. I'll DM you a link to create a support ticket and we'll get back to you on the ticket.

[spice plaza]

Hello @soft mesa, we have sent you a direct message, please check it at https://discord.com/channels/@me/1398158629508747265

• 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.