Test data

Our sandbox environment has a variety of shortcuts that can be triggered by the customer's email address to enforce a specific user flow for testing. Generally, these can be seen through https://demo.slope.so/ by selecting from the dropdown.

A more detailed list is described below.

Customer Eligibility

Order Rejections

Rejection reasons a customer may experience when going through the checkout flow.

Reauthentication and Reevaluation

Linked bank accounts on occasion will disconnect, and customers periodically need to reauthenticate their accounts with Plaid. In addition, generally every 30 days a customer is reevaluated and reunderwritten in order to have the most accurate set of limits.

In sandbox, this is off by default to reduce friction around testing. Here's how to explicitly opt-in to these flows.

Reauthentication

To simulate a reauthentication flow, add the following email shortcut to the customer email on creation:

{any}+always-reauth

Then:

1. Create a customer intent token and open the widget in the payment_methods flow, allowing payment methods to be managed.
2. Link a bank account through the Plaid connection. With the above email shortcut, any added bank accounts will be linked as needing reauthentication.
3. Create an order and go through the checkout flow with an order intent. The user will then be shown the reauthentication screen.

*if no bank accounts are added prior to going through the checkout flow, unexpected behavior may occur.

Reevaluation

When the following email shortcuts are detected, the following behavior occurs:

1. Any created orders will be in the pending state
2. When going through the checkout flow with an order intent, the user will be shown the reevaluation flow and be unable to check out until they have been reevaluated.

*Once you go through the reevaluation flow as a test customer, the reevaluation will not be triggered again.

Plaid Account Credentials

We integrate with Plaid to link bank accounts, and in various flows we redirect the user to Plaid, which prompts for bank account credentials.

Use the following username : password combinations to get the associated behavior described.

Payment Methods

In the sandbox environment, you may use different payment method values to trigger failures modes. The other fields (password, CVV, exp dates, etc) can be any value.