#aaparth_api

1 messages ¡ Page 1 of 1 (latest)

tame crescentBOT
#

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

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

calm knotBOT
urban thistle
#

You want to update the statement descriptor for a single Subscription or for all your Subscription (at Acount level?)

brave crane
#

at account level and I did changed it under public settings on Dashboard

#

but its still showing the older one

urban thistle
urban thistle
#

Is this the new statement descriptor Fliitt

brave crane
#

Following is my code and when I try to put it here it give me error

const subscription = await stripe.subscriptions.create({
default_payment_method: payment_method_id,
customer: customer_id,
items: [{
price: stripe_price_id,
quantity: item_quantity,
}],
promotion_code: stripe_promo_code_id,
expand: ['latest_invoice.payment_intent'],
billing_cycle_anchor: next_month_timestamp,
statement_descriptor_suffix: "Fliitt"
});

urban thistle
brave crane
#

okay so what should I do then ?

urban thistle
#

I see that your account has Fliit as a statement descriptor for now.

brave crane
#

yes

urban thistle
#

Unfortunately banks and card issuers will sometimes display the wrong friendly name (statement descriptor) for some transactions.

brave crane
#

let me share the screenshot

urban thistle
#

And Stripe has no control over the mapping systems banks and card issuers use to produce friendly names for their cardholders, and the friendly names displayed often use multiple data points from a transaction to determine which friendly name to display (only one of which may be the statement descriptor)

brave crane
urban thistle
#

Yes that's good, I just double checked your account

#

For the Subscription Id you've shared with me su_1OtTaDCmxQwltEUMUNjKb5yY, let's check the statement descriptor that was sent to the bank network

brave crane
#

okay

urban thistle
#

it's at latest_invoice.charge

#

we need to check calculated_statement_descriptor

brave crane
#

okay

urban thistle
#

I see GYMBUDDY

brave crane
#

yeah that's wrong

urban thistle
#

When did you make the change on the statement descriptor? before or after the creation of that invoice ?

brave crane
#

before few days

#

may be 15 days ago

urban thistle
#

So the GYMBUDDY is you old statement descriptor ?

brave crane
#

yes

urban thistle
#

Let me check...

#

The update of your statement descriptor was in fact at 2024-02-08 10:07:39 UTC

brave crane
#

yes

urban thistle
#

Well I think you should reach out to Stripe Support at https://support.stripe.com/contact and double check this, I don't see any particular issue from an API integration perspective.

brave crane
#

thank you @urban thistle

#

I will get it to them then