FINITY INTEGRATION MANUAL

Updated November 2026

SOLUCIONES DE PAGOS Y RECAUDOS S.A.S. – “FINITY”

Version 1.0 · Effective November 5, 2026

‍

Connect your company to Finity

‍

This manual explains how to connect to Finity and what you need to have ready before operating in production. It covers the general process; the technical details of each service are in our official documentation, which forms part of this manual in its current version:

‍

‍

1. Ways to connect

‍

You can work with Finity in three ways, depending on what your company needs:

‍

  • Business portal. To manually manage accounts, conversions, payments, withdrawals, transactions and payment links.
  • REST API. To automate, from your own systems, balance inquiries, registration of external accounts, rates and conversions, withdrawals, payment links and transactions.
  • Host to Host (H2H). For exchanging information with financial institutions, when provided for in the agreement.

‍

2. Environments

‍

We have two environments. In sandbox (https://sandbox.dev.finity.com.co) you can run all the tests you need without moving real money. In production (https://api.finity.com.co) real transactions are executed.

‍

The API is REST, responds in JSON format and uses standard HTTP methods and status codes. The current version is identified in the path of each service (/v0/).

‍

3. Step by step

‍

  1. Onboarding. You complete the due diligence process (KYB) and sign the agreement.
  2. Test credentials. We send you a client_id and a client_secret for the sandbox environment through a secure channel.
  3. Authentication. With those credentials you obtain a token through the OAuth2 client credentials flow (POST /v0/oauth/token) and send it as a Bearer token in the Authorization header of each request.
  4. Testing. You test in sandbox the flows you will use in your operation.
  5. Go-live. Once testing is complete, we issue your production credentials and enable the contracted services.

‍

4. Security best practices

‍

  • Do not store credentials or tokens in source code or repositories.
  • Use different credentials for sandbox and production, and store them separately.
  • Always connect to the API over HTTPS.
  • Limit access to credentials to the people who really need it.
  • If you suspect a credential has been compromised, write to us immediately at soporte@finity.com.co so we can revoke it.

‍

5. New versions

‍

We may release new versions of the API and retire obsolete services. When a change affects your integration, we will notify you with a reasonable transition window and updated documentation. Urgent changes required for security reasons may be applied immediately.

‍

6. Support

‍

If you need help with your integration, write to us at soporte@finity.com.co. Response times are those set out in the service level agreement of your contract, according to the severity of the case.

‍

This English version is provided for convenience. In case of any discrepancy, the Spanish version shall prevail.