We are very excited that you chose Flexiti to help boost your online sales! Our developer toolkit makes it quick and easy to integrate Flexiti into your e-commerce site. Take a look through our guides and available assets, and your site will be ready in no time.
Overview
Flexiti’s APIs and Plugins provide merchants integration with Flexiti both at the point of sale and existing eCommerce platforms.
...
This guide will help you identify the steps required to use Flexiti’s APIs and plugins.
Authentication
The Flexiti API uses API keys to authenticate requests. Your keys consist of a Client ID and a Client Secret. You can view and manage your API keys in our Developer Portal.
Every account is provided with two sets of keys. One for testing in our TRAINING environment and one for running live transactions in our PRODUCTION environment.
Obtaining your Flexiti API Keys
Go to our Developer Portal
Create a Developer Portal Account to receive API keys and set up your Trust URL (or IP).
Be sure to keep them secure!
Review the API or Plugin documentation
Implement the TRAINING (test) version on your Staging environment and test thoroughly
Implement the PROD (live) version on your Production environment and review
TRAINING and PRODUCTION environments
...
Environments
Developers have access to three different environments: TRAINING, MERCHANT INTEGRATION, and PRODUCTION.
All API requests exist in TRAINING, MERCHANT INTEGRATION, and PRODUCTION environments. All objects - customers, plans, transactions, etc. created in one environment don’t do not exist in the otherothers. The TRAINING and PRODUCTION environments function almost identically, with a few necessary differences.
In our TRAINING environment:
...
Our TRAINING environment:
For most Online API and Plugin implementations, our Training environment will be the best environment to develop your Flexiti project in.
This environment is a sandbox for testing that uses the same code base as our current production environment.
Transactions and customer accounts generated in this environment are only treated as test objects and is test data is scrubbed daily.
Note |
---|
Maintenance windows in our |
...
Training environment will be communicated ahead of time. |
Our MERCHANT INTEGRATION environment:
For most POS API implementations, our Merchant Integration environment will be the best environment to develop your Flexiti project in.
This environment is considered a “test” environment
In our PRODUCTION environment:
a sandbox for integrating new features for upcoming Flexiti releases.
We introduce pre-release code to this environment to give Merchants an opportunity to integrate the new features and functionality ahead of our Production release.
Note |
---|
Our Merchant Integration environment has a standing maintenance window scheduled Monday and Wednesday mornings. Implementation teams can expect some instability during this time. |
Our PRODUCTION environment:
This environment is the “Live” production environment.
Customer accounts generated in this environment hit the Credit Bureau and any Transactional data generated in this environment are stored in Flexiti’s production systemsThis environment is considered a “Live” production environmentis real.
Note |
---|
Maintenance windows in our Production environment will be communicated ahead of time. |
Authentication
The Flexiti API uses API keys to authenticate requests. Your keys consist of a Client ID and a Client Secret. You can view and manage your API keys in our Developer Portals.
Obtaining your Flexiti API Keys
The first step towards implementation would be to reach out implementation@flexiti.com to create an account in the Flexiti Developer Portal.
Upon setting up your account you will be provided with a set of API keys (Client Secret and Client ID) for our training environment. You will use these keys during your implementation, and any applications generated using these keys will be for testing purposes only.
Be sure to keep them secure!
...
Review the API or Plugin documentation for any other specific Account Setup requirements.
Available Documentation:
Child pages (Children Display) | ||||
---|---|---|---|---|
|