Certification Process

Certification is the joint validation process between the API Broker team and the partner's technical team, carried out before going live in production. Its goal is to verify that the integration works correctly across all critical flows, that webhooks respond as expected, and that the system is ready to operate with real users.

This is not a formal procedure — it is a collaborative working session where real-world scenarios are simulated and issues are identified and resolved before go live.

When does certification take place?

Certification happens once the partner has completed development on the Staging environment and considers the integration ready. It is the step immediately before production credentials are issued.

NDA Signing → Staging Credentials → Development → Certification → PRD Credentials → Beta → Go Live

Prerequisites

Before starting certification, the partner must have the following integrated and working in Staging:

Complete onboarding: person registration, documentation, investment account, and bank account
deposit_create webhook configured and returning HTTP 200
investment_account_update webhook configured and returning HTTP 200
Cash In flow working (at least one deposit credited in Staging)
All contracted modules integrated: Balance Remuneration, Mutual Funds, MEP Dollar, and/or Trading
withdraw_request_update webhook configured if the partner enables withdrawals
Status handling implemented in the partner's UI

If any of these points are not ready, coordinate with your account manager before scheduling the session. An incomplete certification generates rework and delays go live.

Scenarios to be validated

Onboarding

Scenario	What is verified
Individual person registration	Required fields, PEP, FATCA, OECD
Legal entity registration	Corporate data, ultimate beneficial owner, documentation
Document upload	Identity (ID + selfie) and corporate contracts
Investment account creation	Investment profile, `investment_account_id` generated
`investment_account_update` webhook	Correct reception and event processing
Bank account creation	Same-name validation, `bank_account_id` generated
Error cases	Response to duplicate CUIT, missing documentation, invalid CBU

Cash In

Scenario	What is verified
ARS deposit	Correct credit to investment account
USD deposit	Correct credit to investment account
`deposit_create` webhook	Reception, correct parsing, and HTTP 200 response
Webhook idempotency	Behavior when the same event is re-sent
Deposit from unregistered CUIT	Handling of cases where the depositor has no account

Operational modules (depending on contracted modules)

Scenario	What is verified
Balance Remuneration activation	T&Cs accepted, active flag, `minimum_left` and `currency_id` parameters
Mutual fund subscription	Endpoint, ACDI/SIMPLE method, correct request body
Mutual fund redemption	Full and partial redemption, `by_share_quantity`
MEP Dollar purchase	Quote query, order instruction, T+0 settlement
MEP Dollar sale	Reverse flow, ARS credit
Buy order (Trading)	Order submission, status handling
Sell order (Trading)	Order submission, status handling
Order status handling	`SENDING_PENDING`, `OFFERED`, `COMPLETED`, `REJECTED`, `EXPIRED`

Cash Out

Scenario	What is verified
ARS withdrawal	Request, `IN_PROGRESS` and `COMPLETED` statuses
USD withdrawal	Request, `IN_PROGRESS` and `COMPLETED` statuses
`withdraw_request_update` webhook	Correct reception and processing
Rejected withdrawal	Handling of `REJECTED` status and `status_message`
Withdrawal to non-same-name account	Behavior when validation fails
Duplicate `external_id`	Idempotent behavior on retry

Load and robustness tests

Scenario	What is verified
Request duplication	The system does not generate duplicate operations
Timeouts and retries	The partner correctly handles retries without duplicating
Webhook bursts	The partner's URL responds correctly to multiple simultaneous events
Balance reconciliation	Back Office balances match API balances

Session process

Certification is conducted jointly between the partner's technical team and the API Broker team. The typical flow is:

Kickoff: the API Broker team reviews the scenarios to be validated and confirms the environment.
Scenario execution: cases are covered one by one. The partner executes operations from their integration while API Broker verifies the result on the platform side.
Observations log: any failing points are documented in detail for the partner to fix.
Re-validation: once the pending points are resolved, the affected scenarios are re-executed.
Approval: when all critical scenarios are validated, API Broker approves the certification and proceeds with issuing production credentials.

Certification may be completed in one or more sessions depending on the complexity of the integration and the contracted modules.

Approval criteria

For certification to be approved, the following criteria must be met:

✅ Complete onboarding works without errors for both individuals and legal entities
✅ All three mandatory webhooks return HTTP 200 and correctly process the payload
✅ At least one deposit was credited and correctly reflected in the partner's UI
✅ All contracted modules execute end-to-end operations without errors
✅ Order and withdrawal statuses are correctly reflected in the partner's UI
✅ The system correctly handles negative final statuses (REJECTED, NOT_SENT, EXPIRED)
✅ No duplication or idempotency issues are detected

Scenarios flagged as minor observations may remain pending for post-go-live correction, at the discretion of the API Broker team.

Certification deliverables

Upon completion of the process, API Broker provides:

Formal approval confirmation
List of resolved and pending observations (if applicable)
Production Credentials: API keys, URLs, and PRD environment configuration
Webhook configuration in production
Account manager assignment for Beta and Go Live support

Frequently asked questions

How long does certification take?

It depends on the number of integrated modules and the state of the integration. A well-developed integration with all modules can be certified in a single 2 to 3 hour session. If there are observations, additional sessions may be required.

What happens if I don't pass certification?

API Broker provides a detailed list of pending points. The partner fixes them in Staging and a new session is scheduled to re-validate only the flagged items.

Can I certify one module and the rest later?

Yes. It is possible to certify modules incrementally. For example, certifying onboarding + balance remuneration first and adding Mutual Funds or Trading in a second stage.

Do I need to prepare anything special for the session?

Have the Staging environment operational, with at least one registered user with an available balance. The API Broker team will coordinate the details before the session.

Contact

To schedule a certification session or inquire about the status of your integration:

📩 [email protected]