data.vendorId — the external id of the product_vendor the routing engine
picked for this deposit (dart, route_fusion, metcap).
The deposit-side counterpart of
"@cfxlabsinc/db/drizzle".WithdrawalMethodVendorId, and it exists for
the same reason: bankId is resolved by LEFT JOIN through
product_vendor.bank_id, which is NULL for every vendor that fronts banks
rather than being one, so a bankId-only branch cannot identify
route_fusion and silently treats it as its default case — which on this
rail means filing the deposit through MetCap.
Optional because it is a jsonb field added after the fact: quotes written
before it shipped carry none, and readers must treat undefined as
"pre-dates the field" and fall back to the bankId behaviour.
data.vendorId— the external id of theproduct_vendorthe routing engine picked for this deposit (dart,route_fusion,metcap).The deposit-side counterpart of "@cfxlabsinc/db/drizzle".WithdrawalMethodVendorId, and it exists for the same reason:
bankIdis resolved by LEFT JOIN throughproduct_vendor.bank_id, which is NULL for every vendor that fronts banks rather than being one, so abankId-only branch cannot identifyroute_fusionand silently treats it as its default case — which on this rail means filing the deposit through MetCap.Optional because it is a jsonb field added after the fact: quotes written before it shipped carry none, and readers must treat
undefinedas "pre-dates the field" and fall back to thebankIdbehaviour.