Overview

The integration flow is primarily related to Frisbii Transform users who want to utilize Frisbii Transform with a new or specific PSP that is integrated via the Integrator. The process involves providing PSP settings to the Integrator and using the Integrator's API for communication and information retrieval.

Detailed Integration Steps

This diagram represents the flow of information and interactions between the Frisbii Transform user, Frisbii Transform, and the Integrator.

1. Provisioning PSP Settings

   • Frisbii Transform users need to provide their PSP settings to the Integrator.
   • The Integrator generates authentication data for Frisbii Transform to use the Integrator's API.

2. Retrieving PSP Setup Information

   • Frisbii Transform makes a fetch call to the Integrator to retrieve necessary information about the PSP setup.
   • This is done using the /Integration Info endpoint.
   • The response includes details such as:
     • Supported PSP methods (e.g., credit card, direct debit).
     • Configuration requirements (e.g., whether refunds are supported).
     • PSP-specific fields (e.g., API keys, security tokens).

3. Storing PSP Settings

   • Frisbii Transform users can save these settings using the /Settings endpoint.
   • Frisbii Transform does not store specific PSP settings (e.g., API keys, tokens).
   • For any edits or checks by Frisbii Transform users, settings are retrieved through the /Settings endpoint.

Key Points

• PSP Settings Management: Frisbii Transform does not use these settings for any direct PSP connection manipulations. The settings are solely managed through a user-friendly interface provided by Frisbii Transform.
• Integrator's Role: The Integrator handles the specific flows with the PSP, ensuring secure and efficient transaction processing.