Private preview

Test your integration Private preview

Validate your automated platform funding in testing environments.

You can test your credit integration in a sandbox environment using the Credit API and following the same steps as live mode:

1. Create a connected account.
2. Request the card _ issuing _ charge _ card capability.
3. Manage the connected account’s credit terms through its CreditUnderwritingRecord and CreditPolicy .
4. Pay off the connected account’s FundingObligation .

Test the Credit APIs on connected accounts

As you test the Credit APIs on connected accounts, consider the following:

• Minute interval support: In testing environments, you can set the credit _ period _ interval of the platform or connected account CreditPolicy to minute to generate a new FundingObligation as often as once every minute and streamline your testing cycle.
• Simulate Issuing transactions: Use the Dashboard or Issuing API in testing environments to simulate issuing spend and disputes . The applicable FundingObligation updates asynchronously in a few seconds to reflect the activity, allowing you to test the webhook event and your handling of it.
• Deactivate after testing: Stripe continues to generate new FundingObligations for as long as the CreditPolicy status for an account remains active, so deactivate the account’s CreditPolicy when you complete your testing.
• Test retention: Stripe deletes prior test FundingObligations after 7 days.
• When you report credit underwriting decisions on test connected accounts, account notices are created. If you let Stripe send regulated emails on your behalf , we send an email to the test connected account. If you send regulated emails yourself , then you can listen to the account _ notice. created webhook event to know when to send a new notice. Credit underwriting decisions made in testing environments on real connected accounts don’t generate any notices.

Test post-funding your platform

You can also simulate your platform’s daily payment of your FundingObligation using the following test capabilities (not applicable in live mode):

• Update Stripe-controlled fields: Update the status and credit _ period _ interval _ count fields of your platform’s CreditPolicy to simulate updates that are normally set by Stripe.
• Deactivate your CreditPolicy: Set your CreditPolicy ’s status to inactive to stop generating new FundingObligations on your platform’s test account.
• Test Post-Funding: Use the /v1/test _ the relevant part of the product _ balance endpoint or add funds using the Dashboard in testing environments to simulate a FundingObligation payment.