Frequently asked questions

Yes, that’s correct. The two main methods are:

• Bulk import using the predefined CSV structure.
• Automated submission through the FCAP API.

The most suitable method depends mainly on the reporting volume and the required level of automation.

Regardless of whether the data is provided via CSV or API, it follows the same validation, review and XML-generation process within the FIU Compliance Automation Portal (FCAP).

With the API model, your system sends the required reporting data to FCAP via the FCAP API. We provide the API endpoints, authentication requirements, expected payload structure, validation rules, error responses and integration support on the FCAP side.

Your technical team would normally be responsible for extracting the required information from your internal systems, mapping it to the required FCAP structure and sending it to the API.

Once FCAP receives the data, it enters the normal platform workflow for validation, review and XML generation.

Under the standard FCAP API integration model, FCAP does not require direct access to your databases or internal systems.

Your system pushes the required reporting data to FCAP through the API. This means we do not require database credentials or direct access to your operational systems as part of the standard integration.

Any development required within your own environment, such as data extraction, transformation, internal mapping, middleware or scheduling, would normally remain on your side unless separately agreed and scoped with us.

Correct. FCAP acts as the preparation and control layer before goAML. The platform receives the reporting data, validates the information, allows internal review of the report and generates the FIU/goAML-ready XML.

The official submission through the goAML portal remains the reporting entity’s responsibility. The final regulatory review and any communication with the FIU also remain the responsibility of the reporting entity and its compliance officer.

FCAP therefore does not replace goAML. It supports and controls the process leading up to the official submission.

The full FCAP API documentation is normally shared during the implementation phase, once the commercial and confidentiality arrangements are in place. This is because the documentation contains technical integration details, authentication requirements and implementation-specific information.

During implementation, we provide the relevant API documentation to the technical team. This documentation includes the endpoint structure, authentication requirements, expected data format, validation rules and error handling.

We can also support the technical team during the integration and testing process. If needed during the evaluation phase, we can provide a high-level API integration overview or discuss the expected data flow in a technical session.

Yes, if the reporting scenario and configured workflow allow it, multiple transactions for the same customer or player can be included in a single report.

However, this does not mean the transactions are merged into one transaction. Each transaction remains a separate entry inside the report, with its own details such as amount, date, time, currency, reference and any other required fields.

For example, if one player has five reportable transactions that belong in the same report, FCAP can prepare one report for that player containing five separate transaction records. The report is single, but the transactions remain individually identifiable within it.

So, grouping happens at the report level, not by collapsing the underlying transactions. FCAP helps structure the report so related transactions are included together while preserving each transaction as a distinct record for review, validation and XML generation.

The onboarding covers the initial work required to configure the reporting entity and prepare the platform for use. This generally includes:

• Initial business and technical discovery.
• Confirmation of the required reporting workflow.
• Environment and entity configuration.
• User, role and access configuration.
• Configuration of the applicable reporting and validation rules.
• CSV/bulk workflow setup where applicable.
• XML-generation testing using sample data.
• Sample-output validation.
• UAT support.
• Administrator and compliance-user onboarding.
• Production activation support.

Where API integration is included, onboarding also covers the FCAP-side API setup, authentication guidance, sample-payload testing, validation and error-response testing, and integration support for the FCAP-side endpoint.