These pages includes test card figures as well as other information to be sure your integration works as prepared. Utilize it to trigger various flows in your integration and make sure these are typically handled appropriately.

Re Re Payment Intents API

While using the Payment Intents API with Stripe’s customer libraries and SDKs, make certain that:

• Authentication flows are triggered whenever required (use the test that is regulatory figures and PaymentMethods.)
  • No verification (standard U.S. card): 4242 4242 4242 4242 .
  • Authentication required: 4000 0027 6000 3184 .

  Charges API

  With all the Charges API with Stripe’s customer libraries and SDKs, make sure:

  • The card Element is passed away precisely to createToken in your submit handler.
  • Within the reaction handler for createToken , card errors are handled and shown precisely.
  • Just tokens that are valid passed away to your server included in re re payment kind distribution.

  Server-side rule

  In your server-side code, make certain that:

  • All requests are increasingly being made effectively. You may think it is beneficial to see your account’s events and logs as you test thoroughly your integration.
  • All errors that are API managed correctly.
  • Appropriate webhooks are managed properly.

  Whenever you’re willing to bring your integration live, change your test secret and publishable API secrets with live people. Real time payments can not be prepared when your integration remains utilizing your test tips.

  Fundamental test card figures

  Genuine card information can not be utilized in test mode. Alternatively, utilize some of the after test card figures, a legitimate termination date as time goes on, and any random CVC number, to produce a effective repayment. Each test that is basic payment country is defined to U.S. if you want to produce test card re payments making use of cards for any other payment countries, use our international test cards.

  We suggest utilizing our test IDs whenever testing your creating and integration fees, in place of moving card information straight to the API. Utilizing these test IDs instead of card figures helps to ensure your manufacturing integration is developed in a PCI compliant manner and it is maybe maybe not planning to manage card information straight. Each test ID is human-readable and represents card information that is tokenized with your client-side libraries ( e.g., Stripe Elements, Stripe.js).

  Global test card figures

  You need to use some of the test that is following to simulate a fruitful payment for various payment nations.

  Regulatory (3D Secure) test card figures

  The after card information tests re re re payments afflicted with regional laws such as for example Strong Consumer Authentication (SCA). Utilize it to test preserving cards because of the Setup Intents API.

  3D safe test card figures and tokens

  Not totally all cards support 3D protected or need you to redirect the consumer with their card issuer’s verification web web web page. Utilize the card that is following to check 3D safe payments—be aware that 3D Secure redirects won’t happen for payments created directly into the Stripe Dashboard.

  All the Visa and Mastercard test cards don’t require authentication through the customer’s card provider.

  Testing for particular reactions and mistakes

  The following test cards can help create re re payments that create particular responses—useful for testing different situations and mistake codes. Verification checks only operate once the needed information is supplied ( e.g., for cvc_check become set to fail, a CVC rule needs to be supplied).

  By default, moving target or CVC data using the card number causes the target and CVC checks to ensure success. If this given info isn’t specified, the worthiness regarding the checks is null . Any termination date as time goes on is regarded as legitimate.

  You are able to offer invalid card details to check certain mistake codes caused by wrong information being supplied. As an example:

  • invalid_expiry_month : make use of an invalid thirty days ( ag e.g., 13)
  • invalid_expiry_year : work with a 12 months in past times (e.g., 1970)
  • invalid_cvc : make use of two digit quantity (e.g., 99)

  Cartes Bancaires test card figures

  In test mode, the test can be used by you cards below to simulate a Cartes Bancaires fee:

  Disputes

  In test mode, you need to use the test cards below to simulate a transaction that is disputed

  Publish either associated with following values for uncategorized_text to check a won or dispute outcome that is lost

  You are able to make use of these values to try dispute results into the Dashboard. Enter one of these brilliant values in to the information that is additional during proof submission and then click Submit proof.

  Rate limitations

  It is very not likely for users to see any price limitations with normal usage of the API, also at high amount. The most frequent reasons for a person to have price restrictions are insects, bulk information fetches, or load testing that is extreme.

  When your needs commence to receive 429 HTTP mistakes, lower the regularity of one’s demands. Each failed demand is completely safe to retry as price restricting happens before virtually any action and stops the demand from being prepared. Whenever cutting your demand regularity, we suggest a backoff that is exponential first waiting one 2nd before attempting once again. If the demand continues to get the exact same response, wait two moments, then four seconds, etc.

  The price limitation in test mode is gloomier compared to one out of real time mode. Us know if you are experiencing rate limits but are unable to determine why, please let.

  Sources

  Use the information that is following testing payments utilizing Sources.

  Redirect sources

  When making a test supply object that runs on the redirect flow ( e.g., perfect), the URL can be followed by you came back within the redirect[url] industry. This contributes to A stripe page that shows information about the API demand, and where you can either authorize or cancel the re payment.

  Authorizing the re re payment redirects one to the Address specified in redirect[return_url] .

  BECS Direct Debit in Australia

  It is possible to develop a test PaymentIntent that either succeeds or fails by doing the annotated following:

  1. Produce a test PaymentMethod because of the test BSB 000-000 and a test account number through the list below.
  2. Utilize the ensuing PaymentMethod in a confirmAuBecsDebitPayment demand to produce the test cost.