Testing
Nothing blocks you from testing with a live card, but we recommend using the Zūm Rails Test Institution.
- If you are using the Connector without a javascript library, you must specify
the parameter
testinstitution=true
in the url. - If you are using the javascript library, you must pass the property
testinstitution:true
in the config parameter.
By doing the configuration above, the first institution on the list will be Zūm Rails Test Institution.
#
Happy path without security questionUsername | Password |
---|---|
zum | rails |
#
Security question single answerThis option is used with institutions that prompt a one-time verification
code/SMS, or a single question, for example:
What is the name of your first pet?
or Confirm your identity on your phone
Username | Password |
---|---|
zumquestionwithsingleanswer | rails |
#
Security question with multiple choices and a single answerThis option is used with institutions that prompt SMS or Email verification when they give a list of options to send the verification code.
Username | Password |
---|---|
zummultiplechoicequestionwithsingleanswer | rails |
#
Security question with multiple optionsThis option is used with institutions that prompt SMS or Email verification when they give a list of phones and a list of options (SMS/Phone Call/Email) to send the verification code.
Username | Password |
---|---|
zumsendtooptions | rails |
#
Other currenciesConsidering all options above, the balance simulated for the account will be using Canadian Dollar as currency, we can allow Zūm Rails Test Institution to support balance information with another currency such as Euro or US Dollar.
Username | Password | Currency |
---|---|---|
zumUSD | rails | US Dollar |
zumEUR | rails | Euro |
zumRandomCurrency | rails | Randomize between Canadian Dollar, US Dollar and Euro |
#
Force Insights Transactions CategorizationThis option forces the Aggregation process to trigger categorization for Insights using the Zūm Rails Test Institution. It allows testing how transactions will be categorized by the Categorization service in a non-production environment. If the customer has configured the Insights webhook, it may be triggered with either a "Failed" or "Completed" event, depending on the categorization result. Please ensure that the aggregation request has the variable GetTransactions set to true.
Username | Password |
---|---|
zumforcecategorization | rails |
#
Simulate Insights Categorization ErrorThis option simulates a transaction categorization failure within the Insights process, following the standard path without a security question. If the customer has configured the Insights Failed webhook, this username can be used to trigger the failure simulation. Please ensure that the aggregation request has the variable GetTransactions set to true.
Username | Password |
---|---|
zumgenericerrorcategorization | rails |