In this article, you'll first find information on how to append your email address to create specific test user cases in the Demo environment. Below, you'll then find demo credentials to provide to be able to progress through the applicant workflow.
Inviting an Applicant to Apply in Demo Environment
When inviting a test user to apply in the demo environment, there are attributes that can be appended to the email used to create specific test cases.
Email addresses used to test in Demo should have some appended information so as to have unique users. This is done by adding a + followed by other inputs before the domain of the email address. If support@sayvero.com were to create a test applicant they would add one of the "append to email" options. For example, the default experience would be created by having the applicant email be support+default@sayvero.com.
Below you'll find the attributes to add to an email address when applying to create these scenarios. You'll want to add the option in the "Append to Email" section to your email as in the example above to create the outputs listed in the table:
Append to Email | Credit Score | Evictions | Public Records | Criminal Records | CollectionAmount |
+default
+ any unique attribute not listed below | 567 | 7 | 0 | 18 | 4000 |
+badboy1
+bad1
+yellow | 724 | 0 | 1 of type 7x | 0 | 83 |
+badboy2
+bad2
+red | 400 | 7 | 0 | 18 | 1400 |
+goodboy
+good
+green | 800 | 0 | 0 | 0 | 0 |
+no-ssn | Prevents Employer/Payroll verification from storing SSN | ||||
+testuser | call BGCC provider, currently TransUnion, with data provided by applicant | ||||
+bdstest01 | 1 State Criminal AK | ||||
+bdstest02 | 0 | ||||
+bdstest03 | 0 | ||||
+bdstest04 | 0 | ||||
+bdstest05 | 1 State Criminal | ||||
+bdsprod01 | 0 County Criminal AK Anchorage | ||||
+bdsprod02 | 1 Count Criminal AK Anchorage | ||||
+badboy3 | 1 without description |
Credentials to Progress through the Applicant Workflow
VEROSnap
There are no credentials needed for VEROSnap. You can use your own government issued document or grab one from the internet. Keep in mind, the Snap test account will always successfully verify the ID unless you flip off the toggle within the Snap modal to test a failure.
VEROLynk (Payroll Provider or Employer)
Depending on the employer or payroll system you choose, you’ll need access to some or all of these credentials:
Email: test1@argyle.com
Username: test_1
Password: passgood
SMS Code: 8081
Phone Number: (800) 900 - 0001
Driver’s License Number: D1230010
Note: The test users provided by Argyle come with personal information that will update some elements of the VERO application, like name and address.
Income Verification (Bank Account Link through Plaid)
Username: user_good
Password: pass_good
SMS Code: 1234
Select 1 or multiple accounts to use.
Background/Credit Check (TransUnion)
SSN: It can be any random 9 digit number but don’t use 123456789
Quiz: Select the 1st answer for each question.
For County Criminal Searches:
Applicant email must be in the format of {something}+bdstest01@something.com to return county criminal records. For no county records use {something}+bdstest04@something.com
Fees/Charges (Stripe Paywall)
For default processing:
Account Number: 4242 4242 4242 4242
MM/YY: any date in the future
CVV: any 3 digit number
Name: anything
For specific card / payment cases:
4000000000000077 | Charge succeeds and funds will be added directly to your available balance (bypassing your pending balance). |
4000003720000278 | Charge succeeds and funds will be added directly to your available balance (bypassing your pending balance). |
4000000000000093 | Charge succeeds and domestic pricing is used (other test cards use international pricing). This card is only significant in countries with split pricing. |
4000000000000010 | The address_line1_check and address_zip_check verifications fail. If your account is blocking payments that fail postal code validation, the charge is declined. |
4000000000000028 | Charge succeeds but the address_line1_check verification fails. |
4000000000000036 | The address_zip_check verification fails. If your account is blocking payments that fail postal code validation, the charge is declined. |
4000000000000044 | Charge succeeds but the address_zip_check and address_line1_check verifications are both unavailable. |
4000000000005126 | Charge succeeds but refunding a captured charge fails asynchronously with a failure_reason of expired_or_canceled_card. Note that because refund failures are asynchronous, the refund will appear to be successful at first and will only have the failed status on subsequent fetches. We also notify you of refund failures using the charge.refund.updated webhook event. |
4000000000007726 | Charge succeeds but refunds are initially held in the pending state. Some time later the refund is released from pending and sends a charge.refund.updated webhook event. |
4000000000000101 | If a CVC number is provided, the cvc_check fails. If your account is blocking payments that fail CVC code validation, the charge is declined. |
4000000000000341 | Attaching this card to a Customer object succeeds, but attempts to charge the customer fail. |
4000000000009235 | Results in a charge with a risk_level of elevated. |
4000000000004954 | Results in a charge with a risk_level of highest. |
4100000000000019 | Results in a charge with a risk_level of highest. The charge is blocked as it’s considered fraudulent. |
4000000000000002 | Charge is declined with a card_declined code. |
4000000000009995 | Charge is declined with a card_declined code. The decline_code attribute is insufficient_funds. |
4000000000009987 | Charge is declined with a card_declined code. The decline_code attribute is lost_card. |
4000000000009979 | Charge is declined with a card_declined code. The decline_code attribute is stolen_card. |
4000000000000069 | Charge is declined with an expired_card code. |
4000000000000127 | Charge is declined with an incorrect_cvc code. |
4000000000000119 | Charge is declined with a processing_error code. |