API and integrations

Connect your products to Tractial’s components: accounts, IBANs, flows, reporting and compliance journeys.

In brief

APIs connect accounts, flows and compliance to the partner product. Technical documentation is not public. Sandbox and docs open after qualification. No availability commitment is published here.

APIs connect Payment.net’s financial components to a SaaS, marketplace, fintech or platform. Integration is assessed according to the project’s scope; access to environments and technical documentation is granted after project qualification.

Integration sequence (simplified)

  1. Account creation

    A business event on the partner side, within the contracted scope.

  2. Webhook

    A status notification, after scoping the useful events.

  3. Payment

    An incoming or outgoing order, according to the activated components.

  4. Reconciliation

    Reporting data sent back to the product.

    See the page

Pseudo-steps, not an interface contract. No secrets, no real payloads.

Components available (examples)

  • Creation and activation of payment accounts
  • Receiving funds and outgoing transfers
  • Webhooks
  • KYC/KYB compliance journeys
  • Reporting and reconciliation

The integration journey

  1. Qualification

    Presentation of the project, flows and users.

  2. Technical scoping

    API scope, environments, webhooks, volumes.

  3. Compliance validation

    Eligibility, responsibilities, contractual agreement.

  4. Test environment

    Integration and operational testing.

  5. Go-live

    Progressive activation according to usage.

  6. Supervision

    Ongoing operational monitoring.

Checklist

Authentication, environments, errors and idempotence are specified during technical scoping, not on this page.

  • Project qualification
  • API, webhook and volume scoping
  • Compliance validation and contract
  • Test environment
  • Progressive activation
  • Supervision

FAQ

Is the API documentation public?

Access to the technical documentation is granted after project qualification. The contact form lets you present your integration needs.

Is a test environment available?

A test environment is provided as part of the integration journey, depending on the project scope.

What are the technical prerequisites?

Integration relies on REST APIs and webhooks; exact prerequisites are specified during technical scoping.

Related pages