Mapping Canadian PAD (ACSS Debit) Bank Fields to Salesforce Custom Fields
When a donor pays via Canadian pre-authorized debit (ACSS Debit), WeGive captures two bank-identity fields that do not exist on US bank accounts:- Institution number — the 3-digit code identifying the Canadian financial institution.
- Transit number — the 5-digit branch number.
How to set this up
Mapping these fields uses the same field-mapping mechanism as every other payment-method attribute (type label, masked account number, expiration date, etc.). A WeGive team member adds two mapping rules for your organization:
The Salesforce field API names depend on your own Salesforce schema —
there is no single universal name. Provide your field API names to the
WeGive team when requesting this mapping.
Once the mapping rules are in place, every Canadian PAD payment method
pushed to Salesforce includes these values in the payload automatically.
No additional configuration is needed on the WeGive side.
Prerequisites
- Your organization’s Salesforce payment-method sync must already be enabled. See the WeGive team if you haven’t set this up yet.
- The target custom fields must already exist on your Salesforce payment-method custom object.
Important notes
- These mapping rules are set up by the WeGive team — they are not self-service from the dashboard.
- The mapping applies to the push (WeGive → Salesforce) direction. Institution and transit numbers are not pulled back from Salesforce into WeGive.
- Only Canadian PAD (ACSS Debit) bank accounts have these fields. US bank accounts use routing numbers instead, which have their own separate mapping.
Sources
- WeGive Salesforce integration — payment-method field-mapping configuration
- WeGive ACSS Debit payment-method architecture — institution_number and transit_number storage
← Back to Integrations