Language selection

Search

FINTRAC API report submission : Methods to report to FINTRAC

Updated September 16, 2024

From: Financial Transactions and Reports Analysis Centre of Canada (FINTRAC)

Learn how to submit financial transaction reports through FINTRAC API report submission, and consult related technical documentation to implement it.

On this page

What is FINTRAC API report submission

FINTRAC API report submission allows for the secure system-to-system transfer of report information to FINTRAC.

You can use API report submission to send FINTRAC the following reports:

However, you must use the paper form to submit Terrorist Property Reports.

Transition periods to implement API report submission

Businesses that submit higher volumes of reports through systems being decommissioned must take into account the following transition periods to complete their implementation of API report submission:

Registering to use FINTRAC API report submission

An application is required to submit reports using FINTRAC's API. At a minimum, one application and secret is required.

Your technical administration needs to access the FINTRAC API portal to receive enrollment instructions and information on how to create an application and secret keys, to authenticate the API submission pathway for you to begin submitting reports.

Access the FINTRAC API portal

Businesses that submit larger volumes of reports and that do not currently have access to FINTRAC API report submission should contact FINTRAC by email at F2R@fintrac-canafe.gc.ca.

Submitting reports through API

In this section

Submitting, changing and deleting reports

There are 2 groups of API endpoints:

Both API endpoints have 3 different actions for report submission:

Transaction submission limits

The transaction submission limits are different for the single API endpoint and the bulk submission:

If the number of transactions exceeds these limits, you must create a new report to include the additional transactions.

Linking transactions across multiple reports

When you create another report because you exceeded the transaction limit, you can link transactions across multiple reports by including the reporting entity report reference number with a suffix (for example, -01, -02, etc.). This will also ensure FINTRAC is aware of linked reports.

If you need to link transactions in multiple reports, you can continue counting transactions incrementally with each report.

Starting action and completing action limits

You can include up to 50 starting actions and 50 completing actions in a single transaction as long as they occurred on the same date and time.

If a transaction has more than 50 starting actions or more than 50 completing actions, you can include these additional starting or completing actions by creating a new transaction in the same report.

Note: Because you must provide a date and time for each transaction, it is understood that all the starting and completing actions within the transaction also occur at this date and time. If this is not the case, then you will need to add a new transaction to the report with the new date and time. This applies even if the number of starting actions or completing actions is under 50.

Technical documentation to implement API report submission

Find the technical documents you'll need to complete the implementation of your API to submit the transaction reports to FINTRAC.

Documentation for all report types
Technical documentation for FINTRAC API report submission: All report types
Documentation type File Date published

Schemas

(Note: These files include content for each report type. Content for report types for which you do not use API report submission may be deleted as necessary.)

Bulk submission schema
(JSON, 2 kb)

Updated on January 19, 2024

Validation message schema
(JSON, 7 kb)

Updated on February 22, 2024

Delete schema
(JSON, 5 kb)

October 23, 2023

Samples

Validation message sample
(JSON, 8 kb)

October 23, 2023

API endpoints (Swagger)

https://www148.fintrac-canafe.canada.ca/swagger

Updated on June 24, 2024

Forms Paper reporting forms Various dates
Documentation for Suspicious Transaction Reports
Technical documentation for FINTRAC API report submission: Suspicious Transaction Reports
Documentation type Web page or file Date published

Validation rules

Suspicious Transaction Reports API validation rules

Updated on September 16, 2024

Schemas

Suspicious Transaction Report schema
(JSON, 58 kb)

Updated on June 24, 2024

Documentation for Large Cash Transaction Reports
Technical documentation for FINTRAC API report submission: Large Cash Transaction Reports
Documentation type Web page or file Date published

Validation rules

Large Cash Transaction Report API Validation rules

October 23, 2023

Schemas

Large Cash Transaction Report schema
(JSON, 22 kb)

Updated on June 24, 2024

Samples

Large Cash Transaction Report sample
(JSON, 6 kb)

Updated on January 19, 2024

Large Cash Transaction Report bulk submission sample
(JSON, 9 kb)

Updated on January 19, 2024

Documentation for Large Virtual Currency Transaction Reports
Technical documentation for FINTRAC API report submission: Large Virtual Currency Transaction Reports
Documentation type Web page or file Date published

Validation rules

Large Virtual Currency Transaction Report API Validation rules

October 23, 2023

Schemas

Large Virtual Currency Transaction Report schema
(JSON, 46 Kb)

Updated on June 24, 2024

Documentation for Electronic Funds Transfer Reports
Technical documentation for FINTRAC API report submission: Electronic Funds Transfer Reports
Documentation type Web page or file Date published
Validation rules Electronic Funds Transfer Reports validation rules Updated on September 16, 2024
Schemas

Electronic Funds Transfer Reports schema
(JSON, 38 kb)

June 24, 2024
Samples

Electronic Funds Transfer Reports sample scenario B1 - Initiation with single transaction (entity to entity)
(JSON, 8 kb)

Electronic Funds Transfer Reports sample scenario B2 – Initiation with multiple transactions (person to person)
(JSON, 8 kb)

Electronic Funds Transfer Reports sample scenario C1 - Final receipt with intermediaries (entity to person)
(JSON, 8 kb)

Electronic Funds Transfer Reports sample scenario C2 - Final receipt with intermediaries (person to entity)
(JSON, 6 kb)

June 24, 2024
Mock form

Electronic Funds Transfer Reports – Initiation mock form
(PDF, 530 kb)

Electronic Funds Transfer Reports – Final receipt mock form
(PDF, 513 kb)

Updated on April 19, 2024
Documentation for Casino Disbursement Reports
Technical documentation for FINTRAC API report submission: Casino Disbursement Reports
Documentation type Web page or file Date published
Validation rules Casino Disbursement Reports validation rules Updated on June 24, 2024
Schemas

Casino Disbursement Reports schema
(JSON, 25 kb)

Updated on June 24, 2024
Samples

Casino Disbursement Reports JSON sample: Scenario B.1: Casino account withdrawal for payout in cash
(JSON, 4 kb)

Casino Disbursement Reports JSON sample: Scenario B.2: Redemption of chips on behalf of another party
(JSON, 5 kb)

Updated on June 24, 2024

Technical support

If you require support, or have questions regarding API report submission, please contact tech@fintrac-canafe.gc.ca.

Related guidance

Related links

Date Modified: