TranzCapture

TranzCapture is an RDC provider for Credit Unions.

Our current implementation for TranzCapture does not have Velocity. Velocity in TranzCapture is on a per account basis. RDC code as it stands right now expects a velocity for a user. You also cannot update velocity via TranzCapture’s api. These differences mean we don’t support displaying or updating of velocity for TranzCapture.

TranzCapture does not allow for the updating of accounts. This means that while we can reject an account in our layer, we are not actually inactivating the account in TranzCapture’s layer.

We expect a CU to use our layer for approving/rejecting accounts. If a CU decides to reject/inactivate an account in the TranzCapture layer they should also reject the account in our layer. If they don’t the account will become rejected the next time the user syncs. If the user hasn’t synced before viewing the user in People then the account will still display as Approved. Accounts that are rejected because they are inactive with TranzCapture will not be able to be re-approved, until the account is Active again in TranzCapture’s layer. This might manifest in some slightly strange behavior in People if they try to re-approve when the account is in inactive status with TranzCapture.

To enable TranzCapture for a Credit Union you need:

Credit Union Id - this is a TranzCapture identifier for the Credit Union License Key - This is the Credit Union’s License key for TranzCapture use Routing Number - The routing number for the credit union

A config will need to be inserted into the tranzcapture_institution_config table.

INSERT INTO tranzcapture_institution_config (institution_id, credit_union_id, license_key, routing_number) 
VALUES (
  ???, -- Institution Id for the CU
  ???, -- TranzCapture Credit Union Id
  ???, -- The Credit Union's License Key for TranzCapture
  ???, -- Routing Number for the Credit Union
  ???); -- Credential Id for the Credit Union. Optional; defaults to standard Banno credentials. See Institution Specific Credentials section for more info

In the grip_admin_institution_user_specific_abilities the velocity_editable and can_edit_approved_accounts fields should always be false for TranzCapture users.

update grip_admin_institution_user_specific_abilities set
  velocity_editable = false,
  can_edit_approved_accounts = false
where institution_id = ???;

Institution Specific Credentials

Integration with TranzCapture typically uses a standard set of credentials for Banno. In most cases, no additional setup is required beyond the previously described steps; the credential_id field in the tranzcapture_institution_config table can be omitted allowing it to default to the standard Banno credential id.

However, if a credit union needs to use custom credentials, typically due to integration with a TranzCapture provider with their own credentials, follow these steps:

1. Create Credentials

Insert a record into the remote_deposit_capture database in the tranzcapture_credentials table

insert into tranzcapture_credentials (credential_id, description)
values (
  '', -- credential_id
  ''  -- description
);

credential_id: (UUID) randomly generated UUID used to reference the credentials. Can be generated however you’d like, but save this value because we will need it for further steps.
description: (string): A description of the credentials (e.g., who they’re for, when updated, etc.). This field is metadata not used in code so put something that will be useful for debugging

Save the credential_id value as it will be used for further steps.

2. Insert TranzCapture Config

Insert a record into the tranzcapture_institution_config table as described previously in this document referencing the credential_id column from Step 1 for the column tranzcapture_institution_config.credential_id.

3. Add Credentials to Vault

Add the new credentials to Vault at the path secret/rdc/tranzcapture-credentials/<credentialId> with the key-value pairs username=<username> and password=<password>. The credentialId parameter is the value inserted into tranzcapture_institution_config.credential_id from Step 2.

For example, if you inserted credentials with credentialId=00000000-0000-0000-0000-000000000000 then after this change looking in vault (vault read secret/rdc/tranzcapture-credentials/00000000-0000-0000-0000-000000000000) should show:

username: <desired username>
password: <desired password>

4. Restart `remote-deposit-capture` Service

Any new or updated credential info will require a restart of the remote-deposit-capture service. The service can be restarted using this Jenkins job with the parameters: