Best Practices

If you choose to test logging into merchants within the Knot SDK, there are a number of things to keep in mind before and while doing so.

Ensure testing occurs from devices in the U.S. and with merchant accounts based in the U.S. International devices and accounts are infrequently supported by merchants and/or Knot.
Replicate real-life behavior:
1. Do not attempt to provision multiple cards to the same merchant account multiple consecutive times in a short period. The merchant's fraud rules are likely to prevent this behavior.
2. Do not attempt to provision the same card to multiple different accounts with the same merchant. Similar to the above, the merchant's fraud rule are likely to prevent this behavior.
3. Do not attempt to log in to the same merchant multiple consecutive times in a short time frame on the same device.
4. Do not attempt to log into the a merchant account while on a company VPN.
Ensure the proper personal information (beyond the card information) is being provided to Knot (typically in the call to Switch Card). Many merchants require first name, last name, billing address, and/or phone number to update a card-on-file. The billing address may need to pass Address Verification Service (AVS) checks by the merchant. This information can come from a number of different places depending on your integration with Knot or your server's storage/retrieval of this information from other third parties (e.g. bank partner, processor, etc.).
Ensure the card that is being sent to Knot is active (i.e. not locked/frozen) and has sufficient funds (if a debit card). Many merchants attempt a small authorization hold of $0.01 or $1 on debit or prepaid cards.
If you are testing Knot's web SDK, ensure you are not logged in to the merchant in another browser tab at the same time as when logging in via the SDK.
If you choose to check if your card is actually provisioned to the merchant account after completing the flow in the Knot SDK:
1. Allow a bit of time for the merchant account to update. Certain merchants can take a few minutes for the new card to be reflected in the account.
2. Hard refresh the merchant account page and/or log out and log in again to see the newly provisioned card.

Scenarios & Test Credentials

You can use the below credentials (username and password) to login to a merchant in the Knot SDK and simulate various scenarios.

Scenario	Description	Username	Password
Successful Authentication	Simulate a successful authentication to the merchant.	`user_good`	`pass_good`
Invalid Credentials	Simulate a failed authentication due to invalid credentials.	`credentials`	`failed`
One-Time Password (OTP)	Simulate an authentication that requires an OTP.	`user_good`	`pass_otp`
Account Failure	Simulate a failed authentication due to an issue with the user's merchant account.	`account`	`failed`
Merchant Failure	Simulate a failed authentication due to an issue with the merchant.	`merchant`	`failed`
Too Many Attempts	Simulate a failed authentication due to too many consecutive, failed login attempts.	`too many attempts`	`failed`
Card Not Supported	Simulate a failed card switch due to the card not being supported by the merchant.	`card-not-supported`	`failed`
Card Expired	Simulate a failed card switch due to the card being expired.	`card expired`	`failed`
Insufficient Funds	Simulate a failed card switch due to the card have insufficient funds (for debit & prepaid cards).	`insufficient funds`	`failed`
No Subscription	Simulate a failed card switch due to the user's lack of a paid subscription with the merchant.	`subscription`	`failed`
Subscription Admin	Simulate a failed card switch due to the user's account lacking the proper permissions.	`subscription admin`	`failed`
MassSwitcher With Merchant Accounts	Simulate a successful authentication to a user's keychain with >0 merchant accounts.	`keychain`	`pass_good`
MassSwitcher With Zero Merchant Accounts	Simulate a successful authentication to a user's keychain with zero merchant accounts.	`keychain`	`no_accounts`