#eric.ho

1 messages · Page 1 of 1 (latest)

sick citrusBOT
quaint pond
#

Hi

According to the docs, Stripe have different charges on payments depending on whether a card is international and "premium". How do we determine whether the card is premium or not?
You are referring to what part exactly of the docs?
For currency conversion, I invite you to check this guide:
https://stripe.com/docs/currencies/conversions
E.g. when you create a PaymentIntent you specify a currency, if the customer use a card with another currency, then a currency conversion will be applied

restive dew
#

I don't think the card country is sufficient to determine the currency of the card, or is it?

quaint pond
#

back to your question how to detect card is premium, AFAIK, there is no such information exposed via API

restive dew
#

At the end of the day, what we want to achieve is have the customers pay the Stripe service charges. Base on your answer, there is no way to accurately capture the amount we need to raise in the PaymentIntent to delegate the service charges to customers. Am I right?

errant flint
#

👋 stepping in here

restive dew
#

Hi

errant flint
#

That's correct that we don't expose premium vs. standard in our API right now

#

This is good feedback with the recent price change for these EU cards

#

I'll file some feedback internally with a feature request to get this added

restive dew
#

What about the currency conversion? Is there a way to accurately determine what currency the customer is using?

errant flint
#

The best way to do that is to tokenize the PaymentMethod first and then inspect it in your backend before charging

#

This depends on your integration a little bit

#

Have you already built an integration or are you scoping?

restive dew
#

We are still scoping

errant flint
#

Gotcha and are you intending to use Stripe Checkout or Payment Element or something else?

restive dew
#

We are trying to use Payment Element

errant flint
#

Got it

#

So in that case you have two options

#

That allows you to get the PaymentMethod before confirmation

#

The second option would be to use a SetupIntent to collect the PaymentMethod first, then create/confirm the PaymentIntent after you have inspected that PaymentMethod

restive dew
#

But how does it help, if we can't predict the Stripe charges (which is based on whether a card is standard/premium and what currency the card using) using the PaymentMethod object?

errant flint
#

Just not premium vs standard

restive dew
# quaint pond For sure, nope

@quaint pond pointed out here that the country is not an indicator of whether a currency conversion (and thus additional charges) would take place

errant flint
#

Sorry, I'm talking about fees like international cards. In terms of currency conversion in your Stripe account you will know that based on the presentment currency you use and the settlement currencies that you support

#

So for instance if you are a UK merchant and you charge in USD, you can't settle in USD so you are going to get an FX fee

#

But if you charge in GBP then you won't

#

(assuming you have a GBP bank attached)

restive dew
#

Is it true not only for payout, but also for payments (from customers to us), that whether currency conversion takes place base on our settlement currency, not the card's currency?

errant flint
#

Yes

#

The customer might experience their own FX fee between them and their bank if you present in a currency that requires currency conversion on their part

#

But that doesn't influence you

restive dew
#

We are indeed base in UK. And have USD as our alternate currency. In this case, will there be any currency conversion? (We only charge customers in USD)

errant flint
#

Nope you are good then

#

The only fee you will get is the 1% on payout for using Alternate Currency Payouts

restive dew
#

Very clear. Awesome. So the only thing missing the standard/premium cards. I realise the price update is applied after April. I assume you are planning on exposing this info and possibly be available before that time?

#

currently there is no distinction between standard and premium cards, right?

errant flint
#

I don't know whether there are already plans to expose this difference via the API. I would assume it is on the road map but can't guarantee it. I'll file feedback about this as I noted above and hopefully it will be added as a property on the PaymentMethod API shortly