Payments

The Payment Processor Integrations section allows seamless financial transactions within the platform by allowing users to integrate their chosen payment processors. This feature enhances the platform's functionality by enabling secure and efficient payment collection as part of the user's workflow.

1. Payment Metrics

Total Processors: Displays the total number of payment processors available for integration within the platform.

No. of Integrations: Displays the number of payment processor integrations currently set up and active.

2. Payment Management Actions and Table Functions

Payment Integration Button: Allows users to add new payment processor integrations. Clicking this button initiates the setup process for incorporating a new payment processor into your platform workflows.

• Payment Processor: To integrate, select the payment processing service from the drop-down menu:

  • Stripe

  • Orbipay

• Integration Name: Enter the name of the integration. Must be a unique name, up to 60 characters.

• Client API Key: The API key provided by the payment processor for client-side operations.

• Server API Key: The API key is used for server-to-server communications with the payment processor.

• Client Key (Orbipay): The client key is required for client identification.

• Private Key (Orbipay): A key used for encrypting transactions or data sent to the payment processor.

• Public Key (Orbipay): The counterpart to the private key, used for decrypting data or transactions.

• Note (optional): Additional information or notes about this integration.

• Search Bar: Enables users to quickly find existing integrations by keywords.

Table Functions

Actions:

• Download: Click the download to download the user data in a structured format, such as Excel (*.xls) or CSV (*.csv).

• Settings: Click the gear icon and select the Edit Table Columns to manage the columns displayed under the User List table.

3. Integrated Payment Processor Table

• Name: The name assigned to the payment integration for identification within the platform.

• Processor: The payment processor service integrated, e.g., Stripe, Orbipay.

• Date Added: The date when the payment integration was established in MM/DD/YY format.

• Client API Key: Displays the first two characters of the API key associated with the client side of the integration.

• Server API Key: Displays the first two characters of the API key used on the server side for the integration.

• Client Key: Displays the additional client-specific key, if applicable, for enhanced security or functionality.

• Note: Optional field for any notes or additional information relevant to the integration.

To delete the payment integration, click the applicable row and click the Delete icon.