{"_id":"59f79e3c584eb200345cec43","user":"54e4044e8ef7552300409dcb","version":{"_id":"59f79e3c584eb200345ceaff","project":"59f79e3c584eb200345ceafc","__v":8,"createdAt":"2015-09-17T03:47:20.956Z","releaseDate":"2015-09-17T03:47:20.956Z","categories":["59f79e3c584eb200345ceb3a","59f79e3c584eb200345ceb3b","59f79e3c584eb200345ceb3c","59f79e3c584eb200345ceb3d","59f79e3c584eb200345ceb3e","59f79e3c584eb200345ceb3f","59f79e3c584eb200345ceb45","59f79e3c584eb200345ceb46","59f79e3c584eb200345ceb48","59f79e3c584eb200345ceb49","5aa21b60c0bda0002d1568b6","5afb6888212c690003ae3d3b","5b4bdcd3737d1800031d2293","5b9ed89212362100036b5a1c","5bb29bec77c22500034757ea","5bb29bfe77c22500034757ec","5bc8fa8063924c00186c5ded","5bc8fe9fa472190014a6b103"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"3.1.0","version":"3.1"},"project":"59f79e3c584eb200345ceafc","__v":0,"category":{"_id":"59f79e3c584eb200345ceb45","project":"59f79e3c584eb200345ceafc","version":"59f79e3c584eb200345ceaff","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2017-05-12T16:39:43.277Z","from_sync":false,"order":1,"slug":"guides","title":"Resources"},"parentDoc":null,"githubsync":"","updates":["560717c0b7a1330d0052b245","5653bdd3cf450d1700605958","570faa67d6c6f00e00b9882a","58b51e04c50dd93700dbacdb"],"next":{"pages":[],"description":""},"createdAt":"2015-09-17T05:11:42.781Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":2,"body":"## Address Validation\n\nValid USPS mailable addresses are required for the user's address field in Sandbox.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"address\",\n    \"h-1\": \"Result\",\n    \"0-0\": \"123 Fail Address, Fail City, FS 00000\",\n    \"0-1\": \"Supplied address is invalid / Unable to verify address.\",\n    \"1-0\": \"101 Mission Street, San Francisco, CA 94105\",\n    \"1-1\": \"Validation is successful.\"\n  },\n  \"cols\": 2,\n  \"rows\": 2\n}\n[/block]\n## Sample Virtual Document\n\nFollowing are test values for Virtual Document verification in Sandbox. The last 4 digits of your virtual document must be one of the following values (ex: SSN = 777772222).\n\nNote that you cannot verify real identities and document information in sandbox.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"document_value\",\n    \"h-1\": \"Result\",\n    \"0-0\": \"1111 or any other value\",\n    \"0-1\": \"Validation Fails (i.e. identity related information is a complete fail).\",\n    \"1-0\": \"2222\",\n    \"1-1\": \"Validation is successful.\"\n  },\n  \"cols\": 2,\n  \"rows\": 2\n}\n[/block]\n## Sample Physical Document\n\nTo be able to generate a sample base64, you can go to [Base64 Image](https://www.base64-image.de/). They make it very easy to generate a padded base64 for any image. You can then use that base64 to test with our APIs.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"document_value\",\n    \"h-1\": \"Result\",\n    \"0-0\": \"data:image/invalid;base64,SUQs==\",\n    \"0-1\": \"Validation Fails (i.e. identity related information is a complete fail).\",\n    \"1-0\": \"Any Other\",\n    \"1-1\": \"Validation is successful.\"\n  },\n  \"cols\": 2,\n  \"rows\": 2\n}\n[/block]\n## Sample Social Document\n\nFollowing are test values for Social Document verification in Sandbox.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"document_value\",\n    \"h-1\": \"Result\",\n    \"0-0\": \"https://www.facebook.com/invalid\",\n    \"1-0\": \"https://www.linkedin.com/invalid\",\n    \"2-0\": \"https://twitter.com/invalid\",\n    \"0-1\": \"Validation Fails (i.e. identity related information is a complete fail).\",\n    \"1-1\": \"Validation Fails (i.e. identity related information is a complete fail).\",\n    \"2-1\": \"Validation Fails (i.e. identity related information is a complete fail).\",\n    \"3-0\": \"invalid:::at:::gmail.com\",\n    \"3-1\": \"Validation Fails (i.e. identity related information is a complete fail).\",\n    \"4-0\": \"255.255.255.0\",\n    \"4-1\": \"Validation Fails (i.e. identity related information is a complete fail).\",\n    \"h-2\": \"Document Type\",\n    \"0-2\": \"FACEBOOK\",\n    \"1-2\": \"LINKEDIN\",\n    \"2-2\": \"TWITTER\",\n    \"3-2\": \"EMAIL (supplied via base doc)\",\n    \"4-2\": \"IP (supplied via base doc)\",\n    \"5-0\": \"541-754-3010\",\n    \"5-1\": \"Validation Fails (i.e. identity related information is a complete fail).\",\n    \"5-2\": \"PHONE_NUMBER (supplied via base doc)\",\n    \"6-0\": \"123456\",\n    \"6-1\": \"Validation Succeeds during `SUBMITTED|MFA_PENDING`\",\n    \"6-2\": \"EMAIL_2FA and PHONE_NUMBER_2FA\"\n  },\n  \"cols\": 3,\n  \"rows\": 7\n}\n[/block]\n## Sample Bank login credentials\n\nFollowing are the sample bank login credentials that you can use to test out your bank login implementation.\n\nTest nodes will always have a balance of $800 when first added.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Username\",\n    \"h-1\": \"Password\",\n    \"h-2\": \"MFA\",\n    \"0-0\": \"synapse_good\",\n    \"0-1\": \"test1234\",\n    \"0-2\": \"**again** (to get multiple MFAs) or else **test_answer**\",\n    \"2-0\": \"synapse_good\",\n    \"2-1\": \"test1234_checking\",\n    \"2-2\": \"**again** (to get multiple MFAs) or else **test_answer**\",\n    \"h-3\": \"Bank Name\",\n    \"0-3\": \"fake\",\n    \"2-3\": \"fake\",\n    \"5-0\": \"synapse_nomfa\",\n    \"5-1\": \"test1234\",\n    \"5-2\": \"No multi-factor authentication  (\\\"MFA\\\") is necessary\",\n    \"h-4\": \"Comments\",\n    \"5-3\": \"fake\",\n    \"2-4\": \"Returns only checking accounts between 1-10.\",\n    \"0-4\": \"Returns only 1 checking and 1 savings account.\",\n    \"5-4\": \"Returns only 1 checking and 1 savings account.\",\n    \"3-0\": \"synapse_good\",\n    \"3-1\": \"test1234_savings\",\n    \"3-2\": \"**again** (to get multiple MFAs) or else **test_answer**\",\n    \"3-3\": \"fake\",\n    \"3-4\": \"Returns only savings accounts between 1-10.\",\n    \"4-0\": \"synapse_good\",\n    \"4-1\": \"test1234_random\",\n    \"4-2\": \"**again** (to get multiple MFAs) or else **test_answer**\",\n    \"4-3\": \"fake\",\n    \"4-4\": \"Returns only checking & savings accounts between 1-10.\",\n    \"1-0\": \"synapse_good\",\n    \"1-1\": \"test1234_one\",\n    \"1-2\": \"**again** (to get multiple MFAs) or else **test_answer**\",\n    \"1-3\": \"fake\",\n    \"1-4\": \"Returns either 1 checking or 1 savings account.\",\n    \"6-0\": \"synapse_code_mfa\",\n    \"6-1\": \"test1234\",\n    \"6-3\": \"fake\",\n    \"6-2\": \"123456\",\n    \"6-4\": \"Returns only 1 checking and 1 savings account.\"\n  },\n  \"cols\": 5,\n  \"rows\": 7\n}\n[/block]\n## Sample Force Refresh Balance Credentials\n\nWhen adding a new node, append any of these values to the end of the password.  When doing a `force_refresh` on the node, it will trigger the corresponding responses.\n\nAppending “_sync_balance_higher” to the password (e.g. “test1234_sync_balance_higher) will link a node that will return a node balance between $800- $1500 when doing a “force_refresh” on the node.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Append to Password\",\n    \"h-1\": \"Description\",\n    \"0-0\": \"_sync_balance_higher\",\n    \"1-0\": \"_sync_balance_lower\",\n    \"0-1\": \"added to the end of a password for a balance between $800-1500 when synced\",\n    \"1-1\": \"added to the end of a password for a balance between $10-50 when synced\"\n  },\n  \"cols\": 2,\n  \"rows\": 2\n}\n[/block]\n## Testing Login Sync Error Scenarios\n\nWhen adding a new node, append any of these values to the end of the password.  When doing a `force_refresh` on the node, it will trigger the corresponding error.\n\nAppending “_needs_relink” to the password (e.g. “test1234_savings_needs_relink) will link a node that will return the 401/110 error message when you try doing a “force_refresh”. It falls in line with our current sandbox test values so you can add “_needs_relink” to the end of any of the passwords above.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"HTTP_CODE\",\n    \"h-1\": \"ERROR_CODE\",\n    \"h-2\": \"Append to Password\",\n    \"h-3\": \"Description\",\n    \"0-0\": \"503\",\n    \"0-1\": \"503\",\n    \"0-2\": \"_sync_unavailable\",\n    \"0-3\": \"Refresh unavailable.\",\n    \"1-0\": \"400\",\n    \"1-1\": \"410\",\n    \"1-2\": \"_sync_not_allowed\",\n    \"2-2\": \"_needs_relink\",\n    \"3-2\": \"_sync_unknown_error\",\n    \"1-3\": \"Refresh not allowed.\",\n    \"2-3\": \"Bad credentials.\",\n    \"3-3\": \"Unknown refresh error.\",\n    \"2-0\": \"401\",\n    \"2-1\": \"110\",\n    \"3-0\": \"500\",\n    \"3-1\": \"500\"\n  },\n  \"cols\": 4,\n  \"rows\": 4\n}\n[/block]\n## Testing Bank Login Authentication Error Scenarios\n\nWhen adding a new node, use these sample usernames to trigger the corresponding error.\n\nAdding an ACH node with the username “synapse_no_accounts” will return the 402/460 error message. Any password is acceptable and these error messages are triggered based off of the username.\n[block:parameters]\n{\n  \"data\": {\n    \"0-0\": \"402\",\n    \"0-1\": \"460\",\n    \"0-3\": \"No ACH capable account found\",\n    \"1-0\": \"402\",\n    \"1-1\": \"500\",\n    \"2-0\": \"503\",\n    \"2-1\": \"503\",\n    \"1-3\": \"Either the account is locked or bank is requesting user's attention (because the not set up completely set up or for some other reason).\",\n    \"2-3\": \"Service unavailable due to Bank or Synapse maintenance.\",\n    \"h-0\": \"HTTP_CODE\",\n    \"h-1\": \"ERROR_CODE\",\n    \"h-3\": \"Description\",\n    \"h-2\": \"Username\",\n    \"0-2\": \"synapse_no_accounts\",\n    \"1-2\": \"synapse_bank_request\",\n    \"2-2\": \"synapse_maintenance\"\n  },\n  \"cols\": 4,\n  \"rows\": 3\n}\n[/block]\n## Sample Card Numbers\n\nFollowing are the sample card numbers that you can use to test out your `INTERCHANGE-US` implementation.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Card Number\",\n    \"0-0\": \"9401100999999992\",\n    \"h-1\": \"Type\",\n    \"h-2\": \"Network\",\n    \"0-1\": \"DEBIT\",\n    \"0-2\": \"VISA\",\n    \"1-0\": \"9401101999999990\",\n    \"1-1\": \"DEBIT\",\n    \"1-2\": \"VISA\",\n    \"3-0\": \"9401113999999995\",\n    \"3-1\": \"DEBIT\",\n    \"3-2\": \"VISA\",\n    \"h-3\": \"Permission\",\n    \"0-3\": \"NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)\",\n    \"1-3\": \"CREDIT\",\n    \"3-3\": \"CREDIT-AND-DEBIT\",\n    \"4-0\": \"9401200999999990\",\n    \"4-1\": \"CREDIT\",\n    \"4-2\": \"VISA\",\n    \"4-3\": \"NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)\",\n    \"5-0\": \"9401201999999998\",\n    \"5-1\": \"CREDIT\",\n    \"5-2\": \"VISA\",\n    \"5-3\": \"CREDIT\",\n    \"7-0\": \"9401211999999997\",\n    \"7-1\": \"CREDIT\",\n    \"7-2\": \"VISA\",\n    \"7-3\": \"CREDIT-AND-DEBIT\",\n    \"8-0\": \"9401300999999998\",\n    \"8-1\": \"PREPAID\",\n    \"8-2\": \"VISA\",\n    \"8-3\": \"NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)\",\n    \"9-0\": \"9401301999999996\",\n    \"9-1\": \"PREPAID\",\n    \"9-2\": \"VISA\",\n    \"9-3\": \"CREDIT\",\n    \"11-0\": \"9401311999999995\",\n    \"11-1\": \"PREPAID\",\n    \"11-2\": \"VISA\",\n    \"11-3\": \"CREDIT-AND-DEBIT\",\n    \"12-0\": \"9021100999999992\",\n    \"12-1\": \"DEBIT\",\n    \"12-2\": \"DISCOVER\",\n    \"12-3\": \"NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)\",\n    \"13-0\": \"9021101999999990\",\n    \"13-1\": \"DEBIT\",\n    \"13-2\": \"DISCOVER\",\n    \"13-3\": \"CREDIT\",\n    \"15-0\": \"9021111999999999\",\n    \"15-1\": \"DEBIT\",\n    \"15-2\": \"DISCOVER\",\n    \"15-3\": \"CREDIT-AND-DEBIT\",\n    \"16-0\": \"9021200999999990\",\n    \"16-1\": \"CREDIT\",\n    \"16-2\": \"DISCOVER\",\n    \"16-3\": \"NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)\",\n    \"17-0\": \"9021201999999998\",\n    \"17-1\": \"CREDIT\",\n    \"17-2\": \"DISCOVER\",\n    \"17-3\": \"CREDIT\",\n    \"19-0\": \"9021211999999997\",\n    \"19-1\": \"CREDIT\",\n    \"19-2\": \"DISCOVER\",\n    \"19-3\": \"CREDIT-AND-DEBIT\",\n    \"20-0\": \"9021300999999998\",\n    \"20-1\": \"PREPAID\",\n    \"20-2\": \"DISCOVER\",\n    \"20-3\": \"NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)\",\n    \"21-0\": \"9021301999999996\",\n    \"21-1\": \"PREPAID\",\n    \"21-2\": \"DISCOVER\",\n    \"21-3\": \"CREDIT\",\n    \"23-0\": \"9021311999999995\",\n    \"23-1\": \"PREPAID\",\n    \"23-2\": \"DISCOVER\",\n    \"23-3\": \"CREDIT-AND-DEBIT\",\n    \"24-0\": \"9501100999999991\",\n    \"25-0\": \"9501101999999999\",\n    \"27-0\": \"9501111999999998\",\n    \"28-0\": \"9501200999999999\",\n    \"29-0\": \"9501201999999997\",\n    \"31-0\": \"9501211999999996\",\n    \"32-0\": \"9501300999999997\",\n    \"33-0\": \"9501301999999995\",\n    \"35-0\": \"9501311999999994\",\n    \"24-1\": \"DEBIT\",\n    \"24-2\": \"MASTERCARD\",\n    \"24-3\": \"NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)\",\n    \"25-1\": \"DEBIT\",\n    \"25-2\": \"MASTERCARD\",\n    \"25-3\": \"CREDIT\",\n    \"27-1\": \"DEBIT\",\n    \"27-2\": \"MASTERCARD\",\n    \"27-3\": \"CREDIT-AND-DEBIT\",\n    \"28-1\": \"CREDIT\",\n    \"29-1\": \"CREDIT\",\n    \"31-1\": \"CREDIT\",\n    \"32-1\": \"PREPAID\",\n    \"33-1\": \"PREPAID\",\n    \"35-1\": \"PREPAID\",\n    \"28-2\": \"MASTERCARD\",\n    \"29-2\": \"MASTERCARD\",\n    \"31-2\": \"MASTERCARD\",\n    \"32-2\": \"MASTERCARD\",\n    \"33-2\": \"MASTERCARD\",\n    \"35-2\": \"MASTERCARD\",\n    \"28-3\": \"NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)\",\n    \"32-3\": \"NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)\",\n    \"29-3\": \"CREDIT\",\n    \"33-3\": \"CREDIT\",\n    \"31-3\": \"CREDIT-AND-DEBIT\",\n    \"35-3\": \"CREDIT-AND-DEBIT\",\n    \"2-1\": \"DEBIT\",\n    \"2-2\": \"VISA\",\n    \"2-3\": \"DEBIT\",\n    \"2-0\": \"9401110999999991\",\n    \"6-0\": \"9401210999999999\",\n    \"6-1\": \"CREDIT\",\n    \"6-2\": \"VISA\",\n    \"6-3\": \"DEBIT\",\n    \"10-1\": \"PREPAID\",\n    \"10-2\": \"VISA\",\n    \"10-3\": \"DEBIT\",\n    \"10-0\": \"9401310999999997\",\n    \"14-1\": \"DEBIT\",\n    \"14-2\": \"DISCOVER\",\n    \"14-3\": \"DEBIT\",\n    \"14-0\": \"9021110999999991\",\n    \"18-1\": \"CREDIT\",\n    \"18-2\": \"DISCOVER\",\n    \"18-3\": \"DEBIT\",\n    \"18-0\": \"9021210999999999\",\n    \"22-1\": \"PREPAID\",\n    \"22-2\": \"DISCOVER\",\n    \"22-3\": \"DEBIT\",\n    \"22-0\": \"9021310999999997\",\n    \"26-1\": \"DEBIT\",\n    \"26-2\": \"MASTERCARD\",\n    \"26-3\": \"DEBIT\",\n    \"26-0\": \"9501110999999990\",\n    \"30-1\": \"CREDIT\",\n    \"30-2\": \"MASTERCARD\",\n    \"30-3\": \"DEBIT\",\n    \"30-0\": \"9501210999999998\",\n    \"34-1\": \"PREPAID\",\n    \"34-2\": \"MASTERCARD\",\n    \"34-3\": \"DEBIT\",\n    \"34-0\": \"9501310999999996\"\n  },\n  \"cols\": 4,\n  \"rows\": 36\n}\n[/block]\n## Micro-deposit verification\n\nIf a bank account is added with account / routing numbers (instead of online banking logins), we automatically send out micro-deposits to the user's bank account to verify the account. Following are test micro-deposit values for sandbox:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Micro-deposit amount 1\",\n    \"h-1\": \"Micro-deposit amount 2\",\n    \"0-0\": \".10\",\n    \"0-1\": \".10\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]\n## Testing out transaction return scenarios\n\nThese returns are for ACH-US type nodes only. Please remember, in practice ACH returns do not occur in real-time.\n\nWhile testing, [RequestBin](http://requestb.in/) is an excellent tool to help you test out web-hooks for these scenarios.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Amount\",\n    \"h-1\": \"Return\",\n    \"h-2\": \"Return\",\n    \"0-0\": \"222.22\",\n    \"0-1\": \"R01 -- Insufficient Funds\",\n    \"0-2\": \"R01 -- Insufficient Funds\",\n    \"1-0\": \"333.33\",\n    \"1-1\": \"R08 -- Payment Stopped\",\n    \"1-2\": \"R08 Payment Stopped\",\n    \"2-0\": \"444.44\",\n    \"2-1\": \"R10 -- Customer Advises Not Authorized\",\n    \"2-2\": \"R10 Customer Advises Not Authorized\",\n    \"3-0\": \"555.55\",\n    \"3-1\": \"R03 -- No Account/Unable to Locate Account\"\n  },\n  \"cols\": 2,\n  \"rows\": 4\n}\n[/block]\n## Testing out transaction cancellation scenarios\n\nWhile testing, [RequestBin](http://requestb.in/) is an excellent tool to help you test out web-hooks for these scenarios.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Amount\",\n    \"h-1\": \"Cancelation\",\n    \"0-0\": \"111.11\",\n    \"0-1\": \"C10-A -- Please collect ACH auth on sender & then resubmit payment.\",\n    \"1-0\": \"111.12\",\n    \"2-0\": \"111.13\",\n    \"3-0\": \"111.14\",\n    \"4-0\": \"111.15\",\n    \"5-0\": \"111.16\",\n    \"1-1\": \"C46 -- Sender not authorized to make transactions.\",\n    \"2-1\": \"C47 -- Receiver not authorized to make transactions.\",\n    \"3-1\": \"C48 -- Sender on screenings list.\",\n    \"4-1\": \"C49 -- Receiver on screenings list.\",\n    \"5-1\": \"C50 -- Unable to process the transaction (reason undisclosed).\"\n  },\n  \"cols\": 2,\n  \"rows\": 6\n}\n[/block]\n\n## Testing registering a new user fingerprint\n\nNormally when registering a new fingerprint, a random PIN is sent to the specified 2FA device. For testing purposes, it is convenient to know the PIN without checking the 2FA device. If you use this fingerprint the API will always accept the pre-programmed validation PIN.\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"fingerprint\",\n    \"0-0\": \"static_pin\",\n    \"h-1\": \"validation_pin\",\n    \"0-1\": \"\\\"123456\\\"\"\n  },\n  \"cols\": 2,\n  \"rows\": 1\n}\n[/block]","excerpt":"Sample values that you can use while developing on sandbox","slug":"sandbox-test-values","type":"basic","title":"Sandbox Test Values"}

Introduction

Resources

Quickstart Flows

Users

OAuth & Fingerprint

Nodes

Loans

Subnets

Transactions

Remote Deposit Capture

Subscriptions

Statements

UI as a Service

Misc Calls

Sandbox Test Values

Sample values that you can use while developing on sandbox
## Address Validation Valid USPS mailable addresses are required for the user's address field in Sandbox. [block:parameters] { "data": { "h-0": "address", "h-1": "Result", "0-0": "123 Fail Address, Fail City, FS 00000", "0-1": "Supplied address is invalid / Unable to verify address.", "1-0": "101 Mission Street, San Francisco, CA 94105", "1-1": "Validation is successful." }, "cols": 2, "rows": 2 } [/block] ## Sample Virtual Document Following are test values for Virtual Document verification in Sandbox. The last 4 digits of your virtual document must be one of the following values (ex: SSN = 777772222). Note that you cannot verify real identities and document information in sandbox. [block:parameters] { "data": { "h-0": "document_value", "h-1": "Result", "0-0": "1111 or any other value", "0-1": "Validation Fails (i.e. identity related information is a complete fail).", "1-0": "2222", "1-1": "Validation is successful." }, "cols": 2, "rows": 2 } [/block] ## Sample Physical Document To be able to generate a sample base64, you can go to [Base64 Image](https://www.base64-image.de/). They make it very easy to generate a padded base64 for any image. You can then use that base64 to test with our APIs. [block:parameters] { "data": { "h-0": "document_value", "h-1": "Result", "0-0": "data:image/invalid;base64,SUQs==", "0-1": "Validation Fails (i.e. identity related information is a complete fail).", "1-0": "Any Other", "1-1": "Validation is successful." }, "cols": 2, "rows": 2 } [/block] ## Sample Social Document Following are test values for Social Document verification in Sandbox. [block:parameters] { "data": { "h-0": "document_value", "h-1": "Result", "0-0": "https://www.facebook.com/invalid", "1-0": "https://www.linkedin.com/invalid", "2-0": "https://twitter.com/invalid", "0-1": "Validation Fails (i.e. identity related information is a complete fail).", "1-1": "Validation Fails (i.e. identity related information is a complete fail).", "2-1": "Validation Fails (i.e. identity related information is a complete fail).", "3-0": "[email protected]", "3-1": "Validation Fails (i.e. identity related information is a complete fail).", "4-0": "255.255.255.0", "4-1": "Validation Fails (i.e. identity related information is a complete fail).", "h-2": "Document Type", "0-2": "FACEBOOK", "1-2": "LINKEDIN", "2-2": "TWITTER", "3-2": "EMAIL (supplied via base doc)", "4-2": "IP (supplied via base doc)", "5-0": "541-754-3010", "5-1": "Validation Fails (i.e. identity related information is a complete fail).", "5-2": "PHONE_NUMBER (supplied via base doc)", "6-0": "123456", "6-1": "Validation Succeeds during `SUBMITTED|MFA_PENDING`", "6-2": "EMAIL_2FA and PHONE_NUMBER_2FA" }, "cols": 3, "rows": 7 } [/block] ## Sample Bank login credentials Following are the sample bank login credentials that you can use to test out your bank login implementation. Test nodes will always have a balance of $800 when first added. [block:parameters] { "data": { "h-0": "Username", "h-1": "Password", "h-2": "MFA", "0-0": "synapse_good", "0-1": "test1234", "0-2": "**again** (to get multiple MFAs) or else **test_answer**", "2-0": "synapse_good", "2-1": "test1234_checking", "2-2": "**again** (to get multiple MFAs) or else **test_answer**", "h-3": "Bank Name", "0-3": "fake", "2-3": "fake", "5-0": "synapse_nomfa", "5-1": "test1234", "5-2": "No multi-factor authentication (\"MFA\") is necessary", "h-4": "Comments", "5-3": "fake", "2-4": "Returns only checking accounts between 1-10.", "0-4": "Returns only 1 checking and 1 savings account.", "5-4": "Returns only 1 checking and 1 savings account.", "3-0": "synapse_good", "3-1": "test1234_savings", "3-2": "**again** (to get multiple MFAs) or else **test_answer**", "3-3": "fake", "3-4": "Returns only savings accounts between 1-10.", "4-0": "synapse_good", "4-1": "test1234_random", "4-2": "**again** (to get multiple MFAs) or else **test_answer**", "4-3": "fake", "4-4": "Returns only checking & savings accounts between 1-10.", "1-0": "synapse_good", "1-1": "test1234_one", "1-2": "**again** (to get multiple MFAs) or else **test_answer**", "1-3": "fake", "1-4": "Returns either 1 checking or 1 savings account.", "6-0": "synapse_code_mfa", "6-1": "test1234", "6-3": "fake", "6-2": "123456", "6-4": "Returns only 1 checking and 1 savings account." }, "cols": 5, "rows": 7 } [/block] ## Sample Force Refresh Balance Credentials When adding a new node, append any of these values to the end of the password. When doing a `force_refresh` on the node, it will trigger the corresponding responses. Appending “_sync_balance_higher” to the password (e.g. “test1234_sync_balance_higher) will link a node that will return a node balance between $800- $1500 when doing a “force_refresh” on the node. [block:parameters] { "data": { "h-0": "Append to Password", "h-1": "Description", "0-0": "_sync_balance_higher", "1-0": "_sync_balance_lower", "0-1": "added to the end of a password for a balance between $800-1500 when synced", "1-1": "added to the end of a password for a balance between $10-50 when synced" }, "cols": 2, "rows": 2 } [/block] ## Testing Login Sync Error Scenarios When adding a new node, append any of these values to the end of the password. When doing a `force_refresh` on the node, it will trigger the corresponding error. Appending “_needs_relink” to the password (e.g. “test1234_savings_needs_relink) will link a node that will return the 401/110 error message when you try doing a “force_refresh”. It falls in line with our current sandbox test values so you can add “_needs_relink” to the end of any of the passwords above. [block:parameters] { "data": { "h-0": "HTTP_CODE", "h-1": "ERROR_CODE", "h-2": "Append to Password", "h-3": "Description", "0-0": "503", "0-1": "503", "0-2": "_sync_unavailable", "0-3": "Refresh unavailable.", "1-0": "400", "1-1": "410", "1-2": "_sync_not_allowed", "2-2": "_needs_relink", "3-2": "_sync_unknown_error", "1-3": "Refresh not allowed.", "2-3": "Bad credentials.", "3-3": "Unknown refresh error.", "2-0": "401", "2-1": "110", "3-0": "500", "3-1": "500" }, "cols": 4, "rows": 4 } [/block] ## Testing Bank Login Authentication Error Scenarios When adding a new node, use these sample usernames to trigger the corresponding error. Adding an ACH node with the username “synapse_no_accounts” will return the 402/460 error message. Any password is acceptable and these error messages are triggered based off of the username. [block:parameters] { "data": { "0-0": "402", "0-1": "460", "0-3": "No ACH capable account found", "1-0": "402", "1-1": "500", "2-0": "503", "2-1": "503", "1-3": "Either the account is locked or bank is requesting user's attention (because the not set up completely set up or for some other reason).", "2-3": "Service unavailable due to Bank or Synapse maintenance.", "h-0": "HTTP_CODE", "h-1": "ERROR_CODE", "h-3": "Description", "h-2": "Username", "0-2": "synapse_no_accounts", "1-2": "synapse_bank_request", "2-2": "synapse_maintenance" }, "cols": 4, "rows": 3 } [/block] ## Sample Card Numbers Following are the sample card numbers that you can use to test out your `INTERCHANGE-US` implementation. [block:parameters] { "data": { "h-0": "Card Number", "0-0": "9401100999999992", "h-1": "Type", "h-2": "Network", "0-1": "DEBIT", "0-2": "VISA", "1-0": "9401101999999990", "1-1": "DEBIT", "1-2": "VISA", "3-0": "9401113999999995", "3-1": "DEBIT", "3-2": "VISA", "h-3": "Permission", "0-3": "NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)", "1-3": "CREDIT", "3-3": "CREDIT-AND-DEBIT", "4-0": "9401200999999990", "4-1": "CREDIT", "4-2": "VISA", "4-3": "NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)", "5-0": "9401201999999998", "5-1": "CREDIT", "5-2": "VISA", "5-3": "CREDIT", "7-0": "9401211999999997", "7-1": "CREDIT", "7-2": "VISA", "7-3": "CREDIT-AND-DEBIT", "8-0": "9401300999999998", "8-1": "PREPAID", "8-2": "VISA", "8-3": "NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)", "9-0": "9401301999999996", "9-1": "PREPAID", "9-2": "VISA", "9-3": "CREDIT", "11-0": "9401311999999995", "11-1": "PREPAID", "11-2": "VISA", "11-3": "CREDIT-AND-DEBIT", "12-0": "9021100999999992", "12-1": "DEBIT", "12-2": "DISCOVER", "12-3": "NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)", "13-0": "9021101999999990", "13-1": "DEBIT", "13-2": "DISCOVER", "13-3": "CREDIT", "15-0": "9021111999999999", "15-1": "DEBIT", "15-2": "DISCOVER", "15-3": "CREDIT-AND-DEBIT", "16-0": "9021200999999990", "16-1": "CREDIT", "16-2": "DISCOVER", "16-3": "NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)", "17-0": "9021201999999998", "17-1": "CREDIT", "17-2": "DISCOVER", "17-3": "CREDIT", "19-0": "9021211999999997", "19-1": "CREDIT", "19-2": "DISCOVER", "19-3": "CREDIT-AND-DEBIT", "20-0": "9021300999999998", "20-1": "PREPAID", "20-2": "DISCOVER", "20-3": "NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)", "21-0": "9021301999999996", "21-1": "PREPAID", "21-2": "DISCOVER", "21-3": "CREDIT", "23-0": "9021311999999995", "23-1": "PREPAID", "23-2": "DISCOVER", "23-3": "CREDIT-AND-DEBIT", "24-0": "9501100999999991", "25-0": "9501101999999999", "27-0": "9501111999999998", "28-0": "9501200999999999", "29-0": "9501201999999997", "31-0": "9501211999999996", "32-0": "9501300999999997", "33-0": "9501301999999995", "35-0": "9501311999999994", "24-1": "DEBIT", "24-2": "MASTERCARD", "24-3": "NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)", "25-1": "DEBIT", "25-2": "MASTERCARD", "25-3": "CREDIT", "27-1": "DEBIT", "27-2": "MASTERCARD", "27-3": "CREDIT-AND-DEBIT", "28-1": "CREDIT", "29-1": "CREDIT", "31-1": "CREDIT", "32-1": "PREPAID", "33-1": "PREPAID", "35-1": "PREPAID", "28-2": "MASTERCARD", "29-2": "MASTERCARD", "31-2": "MASTERCARD", "32-2": "MASTERCARD", "33-2": "MASTERCARD", "35-2": "MASTERCARD", "28-3": "NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)", "32-3": "NONE (which means both credits and debits have been disabled by cardholder. So adding this card would fail.)", "29-3": "CREDIT", "33-3": "CREDIT", "31-3": "CREDIT-AND-DEBIT", "35-3": "CREDIT-AND-DEBIT", "2-1": "DEBIT", "2-2": "VISA", "2-3": "DEBIT", "2-0": "9401110999999991", "6-0": "9401210999999999", "6-1": "CREDIT", "6-2": "VISA", "6-3": "DEBIT", "10-1": "PREPAID", "10-2": "VISA", "10-3": "DEBIT", "10-0": "9401310999999997", "14-1": "DEBIT", "14-2": "DISCOVER", "14-3": "DEBIT", "14-0": "9021110999999991", "18-1": "CREDIT", "18-2": "DISCOVER", "18-3": "DEBIT", "18-0": "9021210999999999", "22-1": "PREPAID", "22-2": "DISCOVER", "22-3": "DEBIT", "22-0": "9021310999999997", "26-1": "DEBIT", "26-2": "MASTERCARD", "26-3": "DEBIT", "26-0": "9501110999999990", "30-1": "CREDIT", "30-2": "MASTERCARD", "30-3": "DEBIT", "30-0": "9501210999999998", "34-1": "PREPAID", "34-2": "MASTERCARD", "34-3": "DEBIT", "34-0": "9501310999999996" }, "cols": 4, "rows": 36 } [/block] ## Micro-deposit verification If a bank account is added with account / routing numbers (instead of online banking logins), we automatically send out micro-deposits to the user's bank account to verify the account. Following are test micro-deposit values for sandbox: [block:parameters] { "data": { "h-0": "Micro-deposit amount 1", "h-1": "Micro-deposit amount 2", "0-0": ".10", "0-1": ".10" }, "cols": 2, "rows": 1 } [/block] ## Testing out transaction return scenarios These returns are for ACH-US type nodes only. Please remember, in practice ACH returns do not occur in real-time. While testing, [RequestBin](http://requestb.in/) is an excellent tool to help you test out web-hooks for these scenarios. [block:parameters] { "data": { "h-0": "Amount", "h-1": "Return", "h-2": "Return", "0-0": "222.22", "0-1": "R01 -- Insufficient Funds", "0-2": "R01 -- Insufficient Funds", "1-0": "333.33", "1-1": "R08 -- Payment Stopped", "1-2": "R08 Payment Stopped", "2-0": "444.44", "2-1": "R10 -- Customer Advises Not Authorized", "2-2": "R10 Customer Advises Not Authorized", "3-0": "555.55", "3-1": "R03 -- No Account/Unable to Locate Account" }, "cols": 2, "rows": 4 } [/block] ## Testing out transaction cancellation scenarios While testing, [RequestBin](http://requestb.in/) is an excellent tool to help you test out web-hooks for these scenarios. [block:parameters] { "data": { "h-0": "Amount", "h-1": "Cancelation", "0-0": "111.11", "0-1": "C10-A -- Please collect ACH auth on sender & then resubmit payment.", "1-0": "111.12", "2-0": "111.13", "3-0": "111.14", "4-0": "111.15", "5-0": "111.16", "1-1": "C46 -- Sender not authorized to make transactions.", "2-1": "C47 -- Receiver not authorized to make transactions.", "3-1": "C48 -- Sender on screenings list.", "4-1": "C49 -- Receiver on screenings list.", "5-1": "C50 -- Unable to process the transaction (reason undisclosed)." }, "cols": 2, "rows": 6 } [/block] ## Testing registering a new user fingerprint Normally when registering a new fingerprint, a random PIN is sent to the specified 2FA device. For testing purposes, it is convenient to know the PIN without checking the 2FA device. If you use this fingerprint the API will always accept the pre-programmed validation PIN. [block:parameters] { "data": { "h-0": "fingerprint", "0-0": "static_pin", "h-1": "validation_pin", "0-1": "\"123456\"" }, "cols": 2, "rows": 1 } [/block]