AIUNIFY Call Center uses a prepaid credit system to pay for eligible communication and telephony services.
Customers add credits to their account before using services that create usage charges.
Credits may be deducted for activities such as:
The Credits section allows Customers to:
The Customer should maintain enough credits to cover both active usage and recurring telephone-number charges.
Credit and payment-management pages are available to:
Agents cannot manage the Customer’s credit balance through the standard credit-management routes.
Agents may use services that deduct credits from the parent Customer’s balance, but they should not normally:
The Customer account owner should control access to payment and billing information.
The Customer’s credit balance functions as a prepaid account.
The basic process is:
The system prevents normal Customer usage from reducing the account below zero.
If the available balance is lower than the required charge, the transaction or service may be rejected.
Credits pay for usage-based services.
A subscription or service plan may determine which features the account can access, while credits pay for the actual use of eligible communication services.
For example:
Having feature access does not guarantee that the account has enough credits to use the feature.
To open the credit dashboard:
The credit dashboard is located at:
The page displays the Customer’s current balance and available credit-management actions.
The My Credits page may include:
The dashboard loads a recent selection of transactions for quick review.
The complete account statement is available on the Credit History page.
The Current Balance represents the amount currently available for eligible AIUNIFY Call Center services.
For example:
This means the Customer currently has $125.00 in available credits when the platform’s base currency is USD.
The displayed currency follows the platform’s configured base currency and applicable Customer settings.
The amount paid and the amount added to the balance may differ when:
Review the conversion preview before completing a non-base-currency payment.
The My Credits dashboard displays recent financial activity.
A transaction may show:
Use the Account Statement page for the complete transaction history.
The credit dashboard calculates a spending summary for the current month.
The summary may include:
The total amount added during the current month.
The total amount deducted during the current month.
The difference between credits added and credits deducted.
The basic calculation is:
For example:
The number of transactions recorded during the period.
Debit activity may be grouped according to the related service or reference type.
To add credits:
The page is located at:
The Top-Up page displays:
When no payment gateway has been configured, the Top-Up page may display an error such as:
Customers cannot configure the platform’s payment gateways.
To resolve this condition:
Never send card numbers or banking credentials directly to a platform administrator through chat or email.
The Top-Up page displays only payment gateways that have been properly configured by the platform administrator.
Supported gateway integrations in the current source include:
Not every gateway will necessarily appear.
Availability depends on:
To select a gateway:
The first available gateway may be selected automatically.
Confirm the selection before proceeding.
Stripe may support payment by eligible debit or credit cards and other methods enabled in the connected Stripe account.
When using Stripe:
The exact payment methods displayed are controlled by the connected Stripe account.
PayPal may allow the Customer to complete payment through a PayPal account or other payment methods supported by PayPal.
When using PayPal:
Do not close the payment window before PayPal returns the final result.
Razorpay may provide card, bank, wallet, or other payment methods according to the connected account and region.
The Razorpay checkout may open automatically in a secure payment window.
If the window does not appear:
Do not submit the same Razorpay payment repeatedly.
Paystack may support eligible card, bank, transfer, or regional payment methods.
The available methods and currencies depend on the configured Paystack account.
After completing payment, return to AIUNIFY Call Center and confirm that:
Flutterwave may support several regional and international payment methods.
The available currencies and payment methods depend on:
Complete payment only through the secure gateway page opened by AIUNIFY Call Center.
Cryptomus may be used for supported cryptocurrency payments when enabled by the platform administrator.
Cryptocurrency payments may require:
Do not send cryptocurrency to an address copied from an unofficial source.
Confirm the destination inside the secure checkout.
Each payment gateway provides its own list of supported currencies.
The currency selector displays only currencies supported by the selected gateway.
For example, available choices may include:
Changing the payment gateway may also change the available currency options.
AIUNIFY Call Center stores account balances using the platform’s configured base currency.
For example, when the base currency is USD:
The platform administrator controls the system-wide base currency.
The Customer account can store a preferred currency code.
The preferred currency may affect how certain financial information is presented or which currency is initially selected.
However, the actual credit balance remains normalized to the platform’s base currency.
The preferred currency does not change the platform’s underlying accounting currency.
When the selected payment currency differs from the base currency, the Top-Up page requests an exchange-rate preview.
The preview may display:
For example:
This example is illustrative only. The actual rate shown by the system applies at the time of the request.
Exchange rates can change between:
The final credited amount should be based on the payment information and conversion recorded during processing.
Do not rely on an older screenshot or previously displayed rate.
The conversion preview may fail when:
The page may display:
Do not proceed with a non-base-currency payment unless the credited amount is clear.
The standard Top-Up page provides preset amounts such as:
The displayed currency symbol changes according to the selected payment currency.
Select a preset amount to enter it automatically.
Gateway configuration or system changes may produce different preset values.
To use a different amount:
The current interface requires a minimum top-up amount of approximately:
The currency depends on the selected gateway.
Before continuing, the page displays the selected payment amount.
For example:
When paying in a non-base currency, the page may also display the estimated base-currency credits that will be received.
Review both amounts.
To begin checkout:
Click Proceed to Payment only once.
The Customer may be redirected away from AIUNIFY Call Center to the selected payment provider.
This is normal.
The gateway may request:
The Customer should confirm that the gateway page is secure before entering payment information.
A credit top-up may use statuses such as:
The payment has been created but has not yet received final confirmation.
The payment has been confirmed and the credits were added.
The payment was rejected or could not be completed.
The Customer cancelled the checkout or returned without completing payment.
The original payment was reversed according to an approved refund process.
Status availability may differ by gateway.
A Pending transaction does not necessarily mean the payment failed.
It may mean:
Do not immediately repeat a pending payment.
First review:
When payment completes successfully:
A completed transaction should not be manually submitted again.
After a successful gateway payment, the Customer may be returned to:
The page or redirect confirms that payment processing completed or is being finalized.
After returning:
When the Customer cancels the payment, the gateway may return to:
A cancelled checkout should not increase the credit balance.
Before starting another payment:
A payment may fail because of:
The payment provider normally supplies the most specific explanation.
Keep the receipt or confirmation supplied by the payment gateway.
A useful payment record includes:
The gateway receipt and AIUNIFY transaction record should be compared when investigating a discrepancy.
To view the complete transaction history:
The page is located at:
The Account Statement displays the Customer’s financial activity in chronological order, with the newest transactions first.
The statement may include the following columns:
Each record explains how the account balance changed.
A Credit transaction adds funds to the account.
Credit transactions may be created by:
Credit amounts normally display with:
Example:
A Debit transaction removes funds from the account.
Debits may be created by:
Debit amounts normally display with:
Example:
The Description explains the reason for the transaction.
Examples may include:
The wording depends on the service that created the transaction.
The Reference Type connects the transaction to the category of activity that created it.
Examples may include:
The reference helps explain which feature created the credit or debit.
Top-up transactions may display:
The current statement interface recognizes payment gateway labels such as:
Other configured gateways may display their stored identifier or a general gateway label.
The Payment ID can help support personnel locate the transaction at the provider.
Every transaction record stores the balance immediately before the transaction.
For example:
The standard Account Statement interface focuses primarily on Balance After, but Balance Before remains available in the transaction record and CSV export.
Balance After shows the account balance immediately after the transaction was completed.
Example:
Use Balance After to verify that the transaction was applied correctly.
Transactions store a currency code.
Examples include:
Multi-currency top-ups may also record:
The Customer-facing statement may display the normalized base-currency amount rather than every stored conversion field.
The transaction-history backend supports filters including:
The visible filter controls may depend on the current interface version.
Common filter uses include:
Displays money added to the account.
Displays money spent.
Displays transactions during a selected period.
Displays activity related to one service, such as Calls or Top-Ups.
When using date filters:
The system environment may store timestamps in UTC while the browser displays them according to the user’s local settings.
This can cause a transaction near midnight to appear on an adjacent date.
The Customer transaction history can be exported as a CSV file.
The export route is:
The exported filename includes the current date and time.
Example:
The export includes columns such as:
The CSV can be opened in:
The export process can apply the same type and date filters used by transaction history.
To export a specific period:
Keep exported financial files secure.
They may contain transaction references and account activity.
The Customer account supports low-balance settings.
These include:
The threshold determines when the account is considered low.
For example:
When the balance reaches $20.00 or lower, the low-balance process can be triggered.
To configure the threshold:
The current backend accepts a threshold from:
Choose a threshold that reflects the Customer’s normal usage and recurring obligations.
A suitable threshold should consider:
For example, a Customer spending approximately $15.00 per day may choose a threshold higher than $15.00 to avoid a next-day interruption.
The backend checks whether the balance is at or below the configured threshold.
It also prevents the same alert process from running more than once per day.
However, the current source contains a placeholder for the actual Customer notification.
The system currently records the low-balance condition and alert timestamp, but a complete email or in-app notification may not yet be delivered in every installation.
Customers should not rely exclusively on low-balance alerts.
Review the balance regularly.
The current Customer credit controls do not provide a complete automatic-recharge workflow.
The low-balance threshold does not automatically charge a card or payment account.
When the balance becomes low, the Customer must normally open the Top-Up page and complete a new payment.
Call charges may depend on:
Calls may be rounded according to the applicable billing method.
A short call can still produce a minimum billable amount.
SMS charges may depend on:
A message longer than one segment may produce multiple charges.
Review SMS segment counts before bulk sending.
Purchasing a telephone number may create an immediate debit transaction.
The charge may include:
The number should not be assigned unless the Customer has sufficient credits.
Assigned telephone numbers can create recurring monthly charges.
The system reviews assigned numbers and attempts to deduct each number’s monthly cost.
When sufficient credits are available:
When sufficient credits are not available:
Maintain enough credits before the number’s recurring charge is due.
When a service costs more than the available balance, the system may return an error similar to:
The error may include:
To resolve it:
Customer deductions use a protected balance-update process.
The system:
This reduces the risk of two simultaneous services spending the same available credits.
A debit transaction may reference another record such as:
This relationship helps administrators investigate charges.
The Customer statement may display only the reference category rather than a direct link to the related service record.
The system includes a payment-refund route.
Refund availability depends on:
A Customer should not assume that every top-up is automatically refundable.
When a refund is required:
The current Customer interface may not display a self-service Refund button for every gateway.
If top-up credits have already been spent, a full refund may not be possible without adjusting the current account balance.
For example:
Refund processing must account for the credits that were already used.
The administrator and payment gateway determine the permitted result.
An approved refund may produce:
Review both the payment provider and Account Statement after a refund is processed.
An Administrator may manually adjust a Customer’s balance for reasons such as:
Manual adjustments should create transaction records.
Customers cannot normally perform their own manual adjustments.
The Status field describes the transaction’s processing condition.
The credit or debit was successfully applied.
The transaction is awaiting confirmation.
The transaction did not complete.
The original payment was returned or reversed.
The transaction was cancelled before completion.
The exact status values depend on the service and gateway.
To reduce duplicate payments:
A provider timeout does not always mean the payment failed.
When payment succeeded at the gateway but the AIUNIFY balance did not change:
The administrator may need to inspect:
Confirm:
Some gateways provide receipts only through their own customer portal.
Download or save the transaction record when available.
A duplicate payment may occur when:
Record both payment IDs and contact support.
Do not spend disputed duplicate credits until the issue is reviewed.
To investigate:
Avoid reporting only that “the balance is wrong.” Identify the first transaction where it becomes incorrect.
Review:
The debit may have been created by an automated service rather than a manual action taken at that exact moment.
Common causes include:
Review the transaction description and reference type.
A telephone number may be revoked when the Customer does not have enough credits for its monthly charge.
To address it:
A revoked number may not remain available for recovery.
The payment button may remain disabled when:
Correct the required fields before continuing.
A currency may be unavailable because:
Select another gateway or supported currency.
Confirm:
Before retrying, verify that a payment was not already created.
An empty statement normally means:
Clear filters and refresh the page.
Confirm:
Try exporting the complete history without filters.
Customers should protect financial access by:
Review the balance before launching a campaign.
Review the balance before a bulk SMS send.
Maintain enough funds for recurring phone numbers.
Set a practical low-balance threshold.
Do not rely only on the current alert implementation.
Use a small test payment when using a new gateway.
Keep gateway receipts.
Export statements monthly.
Investigate unexpected charges promptly.
Avoid large unused balances when unnecessary.
Document who is authorized to make top-ups.
A Customer should perform a monthly review that includes:
Export the CSV and store it according to the organization’s financial-record policy.
Before starting billable operations, confirm:
AIUNIFY Call Center uses prepaid credits for calls, SMS messages, telephone numbers, AI Agent activity, and other eligible usage-based services.
Customers and Administrators can access credit and payment controls. Agents cannot manage credits through the standard interface.
The My Credits page displays the current balance, recent transactions, monthly spending information, and credit-management actions.
Customers can add credits through configured gateways such as Stripe, Razorpay, Paystack, PayPal, Flutterwave, or Cryptomus.
The Top-Up page supports preset amounts, custom amounts, gateway-specific currencies, and conversion previews when payment is made in a currency different from the platform’s base currency.
Every completed balance change creates a transaction containing the amount, currency, balance before, balance after, description, reference, status, and applicable payment information.
The Account Statement displays credits and debits in chronological order. Transaction records can also be exported to CSV.
Low-balance settings allow the Customer to configure a threshold, but the current source does not yet provide a fully implemented Customer notification in every installation. Customers should monitor balances manually.
Recurring monthly telephone-number charges require sufficient credits. A number may be revoked when the Customer cannot pay its recurring charge.
Customers should review balances before campaigns and bulk messages, retain payment receipts, export statements regularly, and report payment discrepancies before submitting duplicate payments.