Canada: CAD

Supported payment rails

Rail	Description	Settlement	Limit
`CA_EFT`	Electronic Funds Transfer. Business days only. Cut-off ~4:30 PM EST.	T+1	CAD 1,000,000

For details on rail selection, see Payment rail reference.

Beneficiary identity

When creating a beneficiary identity for CAD payments, provide the following fields. See Create and manage identities for the API workflow.

The required fields depend on whether the beneficiary is a business or an individual.

Business beneficiary

Applies to B2B, B2B2B, and C2B2B use cases. Submit a business identity.

Field	Required	Type	Constraints
`businessName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.
`registration`	Required	ARRAY of OBJECT	Each item: `number` (3–35 characters) and `type` (one of `INCORPORATION_CERTIFICATE`, `TAX_ID`). At least one registration entry is required.

Individual beneficiary

Applies to B2C, B2B2C, and C2B2C use cases. Submit an individual identity.

Field	Required	Type	Constraints
`firstName`	Required	STRING	1–140 characters.
`lastName`	Required	STRING	1–140 characters.
`dateOfBirth`	Required	DATE	ISO 8601 date (YYYY-MM-DD).
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Beneficiary financial instrument

When creating a financial instrument for CAD payouts, set financialInstrumentType: CA_EFT and currency: CAD. Provide the following fields in the caEft payment rail object. See Create and manage financial instruments for the API workflow.

Field	Required	Type	Constraints
`bankName`	Required	STRING	2–140 characters.
`institutionNumber`	Required	STRING	Exactly 3 digits.
`transitNumber`	Required	STRING	Exactly 5 digits.
`accountNumber`	Required	STRING	7–12 digits.
`accountType`	Required	ENUM	One of: `CHECKING`, `SAVINGS`.

Originator identity

When creating an originator identity for CAD payments, provide the following fields. The required fields depend on whether the originator is a business or an individual.

Business originator

Applies to B2B, B2B2B, B2B2C, and B2C use cases. Submit a business identity.

Field	Required	Type	Constraints
`businessName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.
`registration`	Required	ARRAY of OBJECT	Each item: `number` (3–35 characters) and `type` (one of `INCORPORATION_CERTIFICATE`, `TAX_ID`). At least one registration entry is required.

Individual originator

Applies to C2B2B and C2B2C use cases. Submit an individual identity.

Field	Required	Type	Constraints
`firstName`	Required	STRING	1–140 characters.
`lastName`	Required	STRING	1–140 characters.
`address.streetAddress`	Required	ARRAY of STRING	Each item 1–70 characters.
`address.city`	Required	STRING	1–140 characters.
`address.stateOrProvince`	Required	STRING	1–140 characters.
`address.postalCode`	Required	STRING	3–15 characters.
`address.country`	Required	STRING	Two-letter ISO 3166-1 alpha-2 country code.

Transaction fields

When creating a payment, provide the following fields. See Create a payment for the API workflow.

Field	Required	Type	Constraints
`purposeCode`	Required	ENUM	See Purpose of payment codes below.
`paymentMemo`	Optional	STRING	0–500 characters. Pattern: `^[\w #@!,.&()\/\\-]{0,500}$`

Purpose of payment codes

Code	Description
`ACCT`	Account management
`EDUC`	Education
`FAMI`	Family support related payments
`FEES`	Payment of fees
`GDDS`	Purchase or sale of goods
`INSU`	Insurance premium
`IVPT`	Invoice payment
`ROYA`	Royalties
`SALA`	Salary payment
`SAVG`	Savings
`SCVE`	Purchase or sale of services
`UBIL`	Utility bill payments

Verifying requirements for your scenario

For the exact fields required for your specific use case and payment rail, use the Payload Schema Utility.