#hhafeez-kanji-descriptors
grand dove
alright
golden yew
Ah, I think it's because its an uncaptured charge:
Statement descriptors for Japanese merchants’ JPY-denominated Visa and Mastercard payments are sent to issuers at time of payment capture
https://stripe.com/docs/statement-descriptors#statement-descriptor-display-timing
Everything else looks fine (JP Visa card, JP merchant)
(you're using capture_method: 'manual')
grand dove
what you are saying is after capturing the payment intent, the statement descriptor will automatically converted to Japanese descriptor.?
golden yew
I believe so yes, according to that doc I linked
Also, it may need to be a JPY presentment currency
You're using USD
grand dove
ohky. let me change this and check this
please check this PI: pi_3LNbAEDBuqP1vtXb0awyKtBb
i cahnge the currency to JPY and also. this order is captured now. but the result is same
@golden yew
golden yew
Checking with a colleague
grand dove
alright
golden yew
To confirm, which field do you expect to see include the kanji descriptor?
Checked with a colleague and we don't actual return/store the used statement descriptor in the API
The network ultimately determines which statement descriptor is shown on the customer's statement, but that's not reflected in the API. Your integration otherwise looks fine
grand dove
i want to show kanji characters with latin against the statement descriptor field
valid hearth
show it where exactly?
grand dove
here in front of Statement descriptor
valid hearth
ok well that's simply a feature request for our dashboard team since it's about what that page in our dashboard shows. I'd suggest writing to https://support.stripe.com/?contact=true with it. You can't do anything about it in your own code.