Note: This document will be updated periodically as new features and functions are added to the Flex platform.
The Finix Flex (Flex) platform provides software companies interested in taking payments in-house with a simple and scalable payments strategy. Flex is a lightweight entry into the payment facilitation model.
This document is a high-level overview of the Flex platform. This document includes API interactions and functionality, as well as workflows. This guide is organized into three sections:
- Creating a merchant
- Creating a buyer
- Processing payments
|Note: The workflows and APIS are available at: https://flex.finixpayments.com/|
The lifecycle of a transaction includes the following events:
- Card authorization and sale
Creating an authorization
An authorization (also known as a card hold) reserves a specific amount on a credit card to be captured at a later date. The creation of an authorization creates a transfer. A transfer represents the flow of funds to or from a payment instrument. A transfer can have four possible state values: PENDING, SUCCEEDED, FAILED, or CANCELED.
Note: The creation of an authorization can be completed via the Flex APIs.
Capturing an authorization
When the authorization is captured, funds are transferred to a resource. The transfer state value is updated from PENDING to SUCCEEDED.
Creating a sale
Note: The creation of a sale can be completed via the Flex APIs.
Creating a settlement
A settlement represents a collection of transfers to be paid out to a specific Merchant. Settlements are created daily.