Definitions

This page defines the main terms used across the portal.

Use it as a quick glossary. Detailed behavior and lifecycle rules are described in the relevant guides.

Core records

• Cardholder: the individual the card is issued to. In the current API schema, card creation identifies the cardholder through person_id or employee_id.
• Person: the person-side customer record.
• Employee: the individual record used for card issuance, linked under a related corporate_id.
• Corporate: the company-side customer record used for account setup.
• Account: the financial account used for card issuance, funding, and transaction activity.
• Card: the payment instrument issued to the cardholder. In card endpoints, the card is identified by token_id.
• External ID (external_id): the partner-defined identifier used when creating person, corporate, and employee records. It is used to map the FINCI record back to the partner's internal record. In the current API schema, it must be unique for that record type.
• Product: the card product configuration used for issuance.

Card state

• Status: the operational usability state of the card.
• Stage: the physical fulfillment state of the card.

Transaction lifecycle

• Authorization: the real-time decision stage for a transaction request. It is not the final booked financial event.
• Authorization advice: the follow-up authorization message carrying the final outcome of the authorization flow.
• Presentment: the clearing-stage event that creates the transaction record used for posting and reconciliation.
• Deferred authorization: a case where presentment arrives without a prior authorization, for example in an offline or in-flight purchase scenario.
• Reversal: an authorization-stage cancellation that unwinds the authorization before presentment and clearing.
• Refund (Return): a credit flow received after the original transaction flow.

API naming

Person and client naming

These guides use person as the business term for the individual customer record.

In the API reference, that same person-side record also appears under client in endpoint names such as /v1/create-client.

This is a naming difference in the API reference, not a separate business object.

Related identifiers remain person-based, such as person_id.

Identifier mapping

• account setup uses person_id or corporate_id
• card creation uses person_id or employee_id, where employee_id is linked under the related corporate_id