Payment Settings

Payment Settings & Gateway Integrations

The Payments module provides a centralized interface for configuring a comprehensive suite of third-party payment gateways—including Tranzila, Kesher, Stripe, Cardcom, PayPlus, Nedarim Plus, Meshulam, and Airwallex—to enable secure transaction processing within the application. By managing these settings, administrators can define specific provider credentials, toggle between Live and Test environments, and designate default gateways for automated billing. This configuration serves as the essential bridge that allows the system to generate payment links, handle external redirects, and process real-time payments directly from document and receipt interfaces.

How to Load the Payments Module

To configure your payment gateways and settings, follow these three steps:

Open User Settings: Click on your profile icon in the top right corner and select the Settings gear icon from the sidebar menu.
Navigate to Payments: Within the Biz1 Settings tab, locate the left-hand sidebar menu and click on the Payments option.
Configure Gateway: In the Payments modal that appears, select your provider from the Payments dropdown, enter the necessary credentials under Payment Detail, and click Save.

Biz1 Payment Configuration

The Biz1 payment option serves as a specialized gateway within the system, typically used for internal processing or specific regional integrations. When this provider is selected, the interface allows you to manage the following:

Payment Detail: This section is used to input your primary merchant credentials for active transactions.
Test Payment Detail: A separate area to input "Sandbox" or developer credentials. This allows you to verify that the connection works perfectly before switching to live billing.
Mode Toggle: Use the Mode (Live/Test) switch to determine which set of credentials the system should use.
Default Setting: Enabling the Default Payment switch ensures that Biz1 is the automatically selected gateway whenever a new payment document or invoice is generated.

Tranzila Express Configuration

Tranzila Express is a comprehensive credit card processing integration that supports advanced billing features. When configuring this gateway, the following specialized fields are required:

Merchant Credentials: You must provide a User Name, Password, and Credit Password for both Live and Test environments.
Express Mode: A checkbox to enable expedited transaction processing (Express) through the Tranzila interface.
Split Payment Method: Allows you to choose how installment payments or split transactions are handled, with options to process By Tranzila or By Biz1.
Environment Management: Use the Mode (Live/Test) toggle to ensure you are testing with your sandbox credentials before moving to production.

Stripe Configuration

Stripe is a global payment processor used for secure online credit card transactions. When setting up this gateway, the interface requires the following credentials for both Live and Test environments:

API Credentials: You must provide a User Name, Password, Key, and Secret Key. These are obtained from your Stripe Dashboard to authenticate the connection.
Dual-Environment Support: The system includes separate fields for Payment Detail (Live) and Test Payment Detail (Sandbox). This allows you to safely test the payment flow without processing actual funds.
Mode Control: Use the Mode (Live/Test) toggle to switch the system between your production account and the testing environment.
Quick Defaults: Enabling Default Payment ensures Stripe is pre-selected as the primary gateway during the document creation and billing process.

Stripe Iframe Configuration

Stripe Iframe is a specialized integration that allows you to embed Stripe's secure payment fields directly into your application's interface. To configure this gateway, the system requires the following:

Secret Key: Unlike the standard Stripe integration, this version specifically requires your Secret Key for both the Payment Detail (Live) and Test Payment Detail (Sandbox) sections.
Secure Embedding: This method is designed to handle payment data securely via an Iframe, ensuring that sensitive card information is processed by Stripe while maintaining a consistent user experience.
Mode & Defaulting: Use the Mode (Live/Test) toggle to manage your environment and the Default Payment switch to ensure this Iframe-based gateway is the primary choice for your billing documents.

Nedarim Iframe Configuration

Nedarim Iframe is a specialized integration that allows you to securely embed the Nedarim Plus payment interface within your system. To set up this gateway, you must provide the following credentials for both Live and Test environments:

MosadID: The unique institution or merchant ID provided by Nedarim Plus.
ApiPass: The API password required to authenticate the transaction request.
ApiValid: A specific validation key or API validation string used to secure the connection.
Setup Management: Use the Mode (Live/Test) toggle to switch between your production and sandbox credentials, and enable Default Payment if you want this to be the primary gateway for your documents.

Payplus Configuration

Payplus is a comprehensive payment clearing solution used for processing various credit card and digital payment types. To configure this gateway, the system requires the following credentials for both Live and Test environments:

Merchant Credentials: You must provide a User Name, Password, Key, and Secret Key issued by Payplus.
Terminal Number: A unique Terminal Number is required to identify the specific merchant terminal for each transaction.
Environment Management: The interface includes separate fields for Payment Detail (Live) and Test Payment Detail (Sandbox). Use the Mode (Live/Test) toggle to control which credentials are currently active.
Automated Selection: Enabling the Default Payment switch ensures Payplus is the pre-selected option when generating new billing documents or invoices.

Kesher Configuration

Kesher is a versatile payment gateway designed to handle integrated credit card processing and specialized installment management. To set up this gateway, you must provide the following credentials for both Live and Test environments:

Merchant Credentials: The system requires a User Name, Password, Key, and Secret Key issued by Kesher.
Kesher Number: You must enter your unique Kesher Number, which serves as your specific merchant identifier within their network.
Split Payment Method: You can choose how to process installment or divided payments by selecting either By Kesher or By Biz1.
Environment Settings: Use the Mode (Live/Test) toggle to switch between active billing and the sandbox testing environment.

Nedarim Plus Configuration

Nedarim Plus is a widely used payment service, especially popular for institutional and community-based collections. To configure this integration, the system requires the following information for both Live and Test environments:

Mosad (Institution ID): Enter the unique institution or merchant identifier provided by Nedarim Plus.
Validation Key: A specific security key used to authorize and validate requests between your system and the Nedarim Plus API.
Environment Settings: Use the Mode (Live/Test) toggle to switch between active transactions and the sandbox environment.
Quick Access: Enabling the Default Payment switch ensures Nedarim Plus is the primary selection for all outgoing invoices and payment requests.

Meshulam Configuration

Meshulam is a popular payment service provider known for its easy-to-use digital payment solutions. To integrate this gateway, the system requires the following details for both Live and Test environments:

Type: A dropdown to select the transaction type, such as For Credit or specific digital payment methods.
Page Code: A unique identifier for your Meshulam payment page that determines the checkout design and settings.
API Key & User ID: Security credentials provided by Meshulam to authenticate your account and process payments securely.
Setup Options: Use the Mode (Live/Test) toggle to manage your integration environment and the Default Payment switch to pre-select Meshulam as the primary gateway for your documents.

Cardknox Configuration

Cardknox is a flexible payment gateway used for processing secure credit card and ACH transactions. To integrate this gateway, the interface requires the following credentials for both Live and Test environments:

Merchant Credentials: You must provide a User Name, Password, Key, and Secret Key. These are found in the Cardknox Merchant Portal to authenticate your transactions.
Parallel Testing Environment: The system provides separate input fields for Payment Detail (Live) and Test Payment Detail (Sandbox), allowing you to verify the integration safely using test cards.
Mode Switch: Use the Mode (Live/Test) toggle to determine whether the system is currently processing real funds or running in simulation mode.
Default Selection: Enabling the Default Payment switch ensures that Cardknox is automatically chosen as the primary processor when generating new billing documents.

Bank Detail Configuration

The Bank Detail option is used to provide manual payment information, such as direct wire transfer or bank deposit instructions, on your generated documents. To configure this, the system requires the following information for both Live and Test environments:

Bank Information: Enter the Bank Name, Bank Code, and Branch Name to identify the specific financial institution.
Account Details: Provide the Account Number and the Mosad (Institution ID) associated with your business account.
Static Instructions: Unlike automated gateways, these details are displayed as text on invoices and receipts to guide customers on where to send manual payments.
Mode & Defaulting: Use the Mode (Live/Test) toggle to manage separate account details for testing, and enable Default Payment to have these bank details pre-selected as the primary payment method.

Paybridge Tranzila Configuration

Paybridge Tranzila is an advanced integration layer for the Tranzila gateway, specifically designed to handle streamlined payment processing. To configure this gateway, the system requires the following information for both Live and Test environments:

Supplier & POS ID: Enter your unique Supplier number and POS ID provided by Tranzila to authenticate your merchant account.
Company Name: Specify the Company name that should be associated with the transaction records and terminal identity.
Dual-Credential Fields: The interface provides separate sections for Payment Detail (Live) and Test Payment Detail (Sandbox). This ensures you can verify your POS settings using test credentials before processing real client payments.
Environment & Defaults: Use the Mode (Live/Test) toggle to switch the active environment, and enable Default Payment to make Paybridge Tranzila the primary choice for automated billing and document payments.

Cardcom Configuration

Cardcom is a specialized payment gateway providing secure credit card clearing and terminal-based processing. To configure this integration, the system requires the following details for both Live and Test environments:

Terminal Number: Enter the unique merchant Terminal Number provided by Cardcom to identify your specific business account.
Merchant Credentials: You must provide the User Name and Password associated with your Cardcom API access to authenticate transactions.
Mode & Testing: Use the Mode (Live/Test) toggle to switch between real transactions and the testing environment. The interface provides dedicated sections for Payment Detail (Live) and Test Payment Detail (Sandbox) to ensure settings are verified before production use.
Primary Gateway: Enabling the Default Payment switch ensures Cardcom is pre-selected as the main payment option when generating new billing documents or invoices.

Payment Gateway Listing Overview

The table at the bottom of the Payments module provides a summary of all configured gateway accounts. This allows you to manage multiple providers and environments from a single view.

Table Columns Breakdown

Name: Displays the custom label you gave to the configuration.This helps distinguish between different accounts from the same provider.
Payment: Shows the gateway provider type (e.g., kesher, Tranzila, airwallex, cardcom).
Mode: Indicates whether the gateway is set to Live (real transactions) or Test (sandbox environment).
Default: A checkbox indicating if this gateway is the primary option automatically selected when creating new invoices or payment documents.
Default Paybridge: Specifically used for Paybridge Tranzila configurations to mark the default terminal for that sub-service.

Action: Provides management tools for each entry:

Edit (Pencil Icon): Opens the configuration fields above to update credentials or settings.
Delete (Trash Icon): Permanently removes the gateway configuration from the system.

Customer Payment & Invoice Process

Based on the customer profile and billing screens, here is the step-by-step workflow for charging a customer and generating documents:

1. Initiate Charge from Profile

- From the Customer Profile, navigate to the Payment tab and select Charge. This opens the transaction interface where you can see the customer's balance and prepare a new billing action.

2. Choose Document Type

In the Invoice section, select the type of document you wish to create:

- Receipt: For simple proof of payment.

- Receipt Tax Invoice: For official tax-compliant billing (as seen in the document creation screen).

3. Select Configured Gateway

The system will display a Payment Gateway dropdown. Here, you select from the providers you previously configured (like Stripe, Cardcom, or Tranzila). The system pulls the active settings and "Mode" (Live/Test) directly from your global configuration.

4. Choose Payment Method & Process

In the final step (as shown in the last image), define the specific Payment Method (e.g., Credit Card, Cash,Transfer ,etc). Once the method is chosen and the amount is confirmed, click Payment to process the transaction and generate the selected invoice or receipt.

Payment Settings