Eranga-balance | Stripe Developers | Page 1

tribal quest Dec 22, 2021, 9:20 AM

#

mainly if you try to call /v1/transfers and don't have enough available balance for the amount you're trying to transfer

carmine marsh Dec 22, 2021, 9:21 AM

#

Great, thanks

#

What about cardholder_phone_number_required ?

tribal quest Dec 22, 2021, 9:22 AM

#

only relevant if you use our Issuing product to issue your own credit cards to providers in your platform

carmine marsh Dec 22, 2021, 9:22 AM

#

So that means the credit card is issued from Stripe?

tribal quest Dec 22, 2021, 9:25 AM

#

yes, it's a product where you can issue a credit card with spending controls, funded from your Stripe account's balance(https://stripe.com/docs/issuing) (e.g. you might use Connect for something like a ride-sharing app where you charge end-customers and then give your service providers a card they can use for expenses or something)

#

that error message is specific to a feature of that product so it's irrelevant if you're not using it

carmine marsh Dec 22, 2021, 9:26 AM

#

Great thanks. How about charge_exceeds_source_limit?

tribal quest Dec 22, 2021, 9:28 AM

#

does the description on that page not make it clear enough? sorry but I don't want to spend the next hour explaining each and every code on that page :p

#

some payment methods have internal transaction limits(for example SEPA Debit I think has a limit of 100,000euro a week initially https://stripe.com/docs/sources/sepa-debit ) and you get that error if you hit it

SEPA Direct Debit payments with Sources

Use Sources to accept payments using SEPA Direct Debit, a popular European banking payment method.

carmine marsh Dec 22, 2021, 9:29 AM

#

Sorry about that. We are going through each and every error code we could get from Stripe. And the ones we don't understand we are asking your help to clarify

#

Because in the API, we don't see which errors we could get if we use a certain endpoint

#

If you could redirect me to something meaningful, that would be a time saver

tribal quest Dec 22, 2021, 9:31 AM

#

yeah I don't think that's the right approach, the right approach is to test your actual code you're using with various test cards (https://stripe.com/docs/testing#cards-responses) or test details for the specific payment methods you use and see what errors can occur in the code paths you use

carmine marsh Dec 22, 2021, 9:32 AM

#

You mean trial and error?

#

That would mean we would have lot of combinations if we check the paths with different types of payment methods etc.

tribal quest Dec 22, 2021, 9:34 AM

#

I would call it robustly testing your code paths

#

I can't see how looking at a long list of error codes when half of them might be for products you don't even use like Issuing is more efficient

#

in any case for 90% of errors the behaviour is mostly the same, show the customer a generic 'payment failed' message, and log the error for your own exception reporting

carmine marsh Dec 22, 2021, 9:46 AM

#

The idea was to identify the errors that might be meaningful to the customer (e.g.: amount_too_large ) so that they know that this is something that they cannot do.

#

I agree that going through this entire list is not that productive since we don't know most of the errors since we are not using all the features Stripe provides.

#Eranga-balance