Our Client libraries raise exceptions for many reasons, such as a failed charge, invalid parameters, authentication errors, and network unavailability. We recommend writing code that gracefully handles all possible API exceptions.
try { // Use Stripe's library to make requests...} catch (CardException e) { // Since it's a decline, CardException will be caught System.out.println("Status is: " + e.getCode()); System.out.println("Message is: " + e.getMessage());} catch (RateLimitException e) { // Too many requests made to the API too quickly} catch (InvalidRequestException e) { // Invalid parameters were supplied to Stripe's API} catch (AuthenticationException e) { // Authentication with Stripe's API failed // (maybe you changed API keys recently)} catch (APIConnectionException e) { // Network communication with Stripe failed} catch (StripeException e) { // Display a very generic error to the user, and maybe send // yourself an email} catch (Exception e) { // Something else happened, completely unrelated to Stripe}