Flutterwave is a payments technology company that provides payment infrastructure and APIs enabling businesses to accept and send payments in Africa and globally.
Flutterwave is a payments technology company that provides payment infrastructure and APIs enabling businesses to accept and send payments in Africa and globally. On Nagent, Flutterwave is exposed as a fully-configurable payment processing integration that any agent can call — 53 actions, and API key authentication. No code is required to wire Flutterwave into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Flutterwave to automate the kinds of tasks payment processing teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Flutterwave into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Flutterwave, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FLUTTERWAVE_CANCEL_PAYMENT_PLANTool to cancel a payment plan. Use when you need to prevent all future subscriptions under this plan.
Input parameters
The unique identifier of the payment plan to cancel.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_CREATE_BENEFICIARYTool to create a new transfer beneficiary. Use when you need to add a beneficiary before making a transfer.
Input parameters
The beneficiary's bank code. Retrieve valid codes via the get_banks endpoint.
The beneficiary's account number. Example: '0690000041'
Optional: The full name of the beneficiary, if different from the account holder name.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_CREATE_BULK_TOKENIZED_CHARGETool to create a bulk tokenized charge batch for charging multiple previously tokenized cards. Use when you need to process multiple recurring or subscription charges in a single batch. Each charge must reference a valid card token obtained from prior tokenization.
Input parameters
Descriptive title identifying this bulk charge batch
List of individual charge items to process. Each must have a unique tx_ref
Configuration for automatic charge retry behavior.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_CREATE_BULK_VIRTUAL_ACCOUNT_NUMBERSTool to create multiple virtual account numbers. Use when you need to generate multiple static virtual accounts for customers in a single request.
Input parameters
Unique reference to identify this batch of virtual accounts.
List of virtual account details for each customer in the batch.
Context or reason for this bulk creation.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_CREATE_PAYMENT_LINKTool to create a hosted payment link. Use when you need a shareable payment URL for one-time transactions.
Input parameters
Amount to charge; must be greater than 0
Unique transaction reference
ISO 4217 currency code
Customer contact information
URL to redirect customer after payment
Optional customization for the payment link.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_CREATE_PAYMENT_PLANTool to create a new payment plan. Use after confirming plan and customer details.
Input parameters
The name of the payment plan. Appears on subscription reminder emails.
The amount to charge each billing cycle. If omitted, uses the amount from subscription initiation.
Currency code (ISO 4217). Defaults to 'NGN'.
The duration in billing cycles. For example, 5 for five months if interval='monthly'. If unset, the plan continues indefinitely.
The billing interval; one of 'hourly', 'daily', 'weekly', 'monthly', 'yearly', 'quarterly', 'bi-annually', or custom like 'every five months'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_CREATE_REFUNDTool to create a refund for a transaction. Use when you need to initiate a refund after confirming the transaction ID and refund amount.
Input parameters
Unique identifier of the transaction to refund
Amount to refund as a string. Must not exceed the original transaction amount.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_CREATE_SUBACCOUNTTool to create a new subaccount. Use when you need to configure split disbursement accounts.
Input parameters
Additional metadata as list of name/value pairs
Country code for the subaccount
Split type: 'percentage' or 'flat'
Split value for disbursement. For 'percentage' type, use decimal format (e.g., 0.10 for 10%, 0.25 for 25%). For 'flat' type, use the actual amount in the local currency.
Bank ISO code for the subaccount
Business name for the subaccount
Bank account number for the subaccount
Business email address
Primary business contact mobile number
Business contact person name
Business contact mobile number
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_CREATE_VIRTUAL_ACCOUNTTool to create a new virtual account number. Use after confirming customer details when assigning a unique account for bank transfers.
Input parameters
Customer's Bank Verification Number; required if is_permanent is true.
Customer's email address.
Exact amount to be collected per transaction (minimum 1).
Merchant's transaction reference to echo with incoming payments.
Number of days before a dynamic account expires.
Customer's last name.
Customer's first name.
Number of times a dynamic account can be used before expiring.
Description shown when retrieving account details.
Customer's phone number with country code.
Set to true for a static (permanent) virtual account; defaults to false (dynamic account).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_DELETE_BENEFICIARYTool to delete a beneficiary by ID. Use when you need to remove a saved transfer beneficiary by its unique ID after confirming the ID.
Input parameters
Unique identifier of the beneficiary to delete, obtained via the list-all-beneficiaries endpoint.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_DELETE_SUBACCOUNTTool to delete a subaccount by ID. Use when you need to remove a subaccount from your Flutterwave account.
Input parameters
The numeric ID of the subaccount to delete (e.g., from the 'id' field returned when creating a subaccount, not the 'subaccount_id' field which starts with RS_)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_DISABLE_PAYMENT_LINKTool to disable a Flutterwave payment link. Use when you need to prevent further payments from an existing link after confirming the link is valid.
Input parameters
The full URL of the payment link to disable.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_FETCH_BENEFICIARYTool to retrieve details of a specific beneficiary by ID. Use after obtaining a beneficiary ID to fetch its full details from Flutterwave.
Input parameters
Unique identifier of the beneficiary to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_FETCH_SUBACCOUNTTool to retrieve details of a specific subaccount by ID. Use when you need full subaccount info after creating or updating splits.
Input parameters
The numeric ID of the subaccount to retrieve (e.g., from the 'id' field returned when creating a subaccount, not the 'subaccount_id' field which starts with RS_)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GENERATE_TRANSACTION_REFERENCETool to generate a unique transaction reference. Use when initiating a new Flutterwave transaction requires a unique reference to prevent duplication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_ALL_SUBSCRIPTIONSTool to retrieve all subscriptions, including cancelled ones. Use when you need a comprehensive list of subscription records for auditing or reporting.
Input parameters
Page number for pagination (>= 1)
Number of records per page (>= 1)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_ALL_TRANSACTIONSTool to retrieve a list of all transactions with optional filters. Use when you need to paginate or filter transaction history after confirming valid API credentials.
Input parameters
Page number to fetch (>= 1)
Filter transactions by status ('successful' or 'failed')
Filter transactions by transaction reference
End date for fetching transactions (YYYY-MM-DD)
Filter transactions by currency (e.g., 'NGN', 'USD')
Start date for fetching transactions (YYYY-MM-DD)
Filter transactions by customer email
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_ALL_WALLET_BALANCESTool to retrieve all wallet balances across currencies. Use when reconciling balances after authentication.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_BALANCES_PER_CURRENCYTool to retrieve wallet balance for a specific currency. Use after transactions to confirm available and ledger balances in a given currency.
Input parameters
Three-letter ISO currency code of the wallet, e.g., 'NGN', 'USD'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_BANK_BRANCHESTool to retrieve branch codes for a specific bank. Use when you need branch information for transfers in countries like Ghana that require branch codes.
Input parameters
Unique identifier of the bank to retrieve branches for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_BANKS_BY_COUNTRYTool to retrieve all banks in a specified country. Use when you need to get available banks for transfers or payments in a specific country.
Input parameters
ISO 3166-1 alpha-2 country code (e.g., NG for Nigeria, GH for Ghana, KE for Kenya, UG for Uganda, ZA for South Africa, TZ for Tanzania).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_BILL_CATEGORIESTool to retrieve available bill categories. Use after authenticating to Flutterwave to display bill payment options to users.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_BULK_TOKENIZED_CHARGETool to retrieve the status of a bulk tokenized charge operation by ID. Use after initiating a bulk tokenized charge to check its processing status.
Input parameters
Unique identifier of the bulk tokenized charge to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_BULK_VIRTUAL_ACCOUNTTool to fetch bulk virtual account details using batch ID. Use this after creating bulk virtual accounts to retrieve the generated account numbers and their details.
Input parameters
Unique identifier for the batch of virtual accounts to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_MULTIPLE_REFUND_TRANSACTIONSTool to retrieve multiple refund transactions with optional filters. Use when you need to fetch paginated refund data after confirming valid API credentials.
Input parameters
Page number for pagination (>= 1)
Filter refunds by status ('completed' or 'pending')
Filter refunds by Flutterwave reference
End date for filtering refunds (YYYY-MM-DD)
Start date for filtering refunds (YYYY-MM-DD)
Number of records per page (>= 1)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_PAYMENT_PLANTool to retrieve details of a specific payment plan by ID. Use after obtaining the payment plan ID to fetch its details from Flutterwave.
Input parameters
Unique identifier of the payment plan to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_PAYMENT_PLANSTool to retrieve a list of all payment plans. Use when you need to fetch and present your account’s configured billing plans.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_REFUNDTool to retrieve details of a specific refund by ID. Use after obtaining the refund ID to fetch its details from Flutterwave.
Input parameters
Unique identifier of the refund to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_TRANSACTIONTool to retrieve details of a specific transaction by ID. Use after obtaining the transaction ID to fetch its details from Flutterwave.
Input parameters
Unique identifier of the transaction to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_TRANSACTION_FEETool to retrieve the fee for a specific transaction. Use when you need to calculate the total charge including fees before initiating the transaction.
Input parameters
The amount to be charged from the customer (must be non-negative)
Currency code in ISO 4217 format, e.g., NGN or USD
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_TRANSFER_FEETool to retrieve the fee for initiating a transfer. Use when you need to estimate transfer costs before creating a transfer. Example: "Calculate the fee for transferring NGN 5000 to an account."
Input parameters
Type of transfer: 'account', 'mobilemoney', or 'barter'.
The amount to be transferred. Must be a positive integer.
ISO 4217 currency code for the transfer (e.g., 'NGN', 'USD').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_TRANSFER_RATESTool to retrieve exchange rates for transfers between currencies. Use when you need to calculate conversion rates before initiating a cross-currency transfer.
Input parameters
The destination amount for which to calculate transfer rates. Must be a positive number.
ISO 4217 currency code for the source currency (e.g., 'NGN', 'KES', 'GHS').
ISO 4217 currency code for the destination currency (e.g., 'USD', 'EUR', 'GBP').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_VIRTUAL_ACCOUNT_NUMBERTool to fetch details of a virtual account number by order reference. Use when you need to retrieve account details after creation.
Input parameters
The order reference returned when the virtual account was created (e.g., URF_1771052916369_342835)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_GET_WALLET_STATEMENTTool to retrieve wallet balance history with optional filters. Use when you need to view transaction history and balance changes over a period.
Input parameters
Page number for pagination
End date for transaction history (format: YYYY-MM-DD)
Filter by currency (e.g., USD, NGN, GHS)
Start date for transaction history (format: YYYY-MM-DD)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_INITIATE_BVN_VERIFICATIONTool to initiate BVN verification consent. Use when you need to verify a customer's Bank Verification Number (BVN) by obtaining their consent first. The customer will be redirected to a consent page where they provide approval to access their BVN data.
Input parameters
The Bank Verification Number (11 digits)
The customer's last name
The customer's first name
The URL where the customer will be redirected after consent is granted or declined
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_INITIATE_MOBILE_MONEY_TANZANIATool to initiate a mobile money payment in Tanzania. Use after collecting customer details to charge via Tanzanian mobile money networks.
Input parameters
Additional custom metadata as key/value pairs
Customer's email address
Amount to charge; must be greater than 0
Unique transaction reference for this payment
Mobile money network, e.g., 'Halopesa'
Currency code in ISO 4217 format; must be 'TZS'
Customer's full name
Customer's IP address
Customer's mobile number in international format (e.g., +255712345678)
Device fingerprint for enhanced fraud detection
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_LIST_ALL_BENEFICIARIESTool to list all saved beneficiaries. Use when you need to retrieve all transfer beneficiaries associated with your account.
Input parameters
Page number for pagination (>= 1)
Number of records per page (>= 1)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_LIST_BILLER_PRODUCTSTool to retrieve all products available under a specific biller. Use after getting bill categories to display available products for bill payment.
Input parameters
Biller code to retrieve products for (e.g., 'BIL136').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_LIST_BILLERSTool to retrieve available billers. Use after authenticating to Flutterwave to display bill payment biller options to users.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_LIST_CHARGEBACKSTool to retrieve a list of chargebacks with optional filtering by Flutterwave reference. Use when you need to view all chargebacks or search for a specific chargeback by transaction reference.
Input parameters
Page number for pagination (>= 1)
Flutterwave reference to filter chargebacks by specific transaction
Number of records per page (>= 1)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_LIST_PAYOUT_SUBACCOUNT_REFUNDSTool to list all payout subaccount refunds with pagination support. Use when you need to retrieve payout subaccount refund history with optional page filtering.
Input parameters
Page number for pagination (>= 1)
Number of records per page (>= 1)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_LIST_PAYOUT_SUBACCOUNTSTool to list all payout subaccounts. Use when you need to retrieve all payout subaccounts associated with your Flutterwave account.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_LIST_RECURRING_BILLSTool to retrieve all recurring bill payments. Use when you need to view scheduled or active recurring billing arrangements.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_LIST_SETTLEMENTSTool to retrieve all settlements with optional filters. Use when you need to fetch settlement records, view transaction settlements, or track payment disbursements.
Input parameters
Page number to retrieve (>= 1)
End date for filtering settlements (YYYY-MM-DD format)
Start date for filtering settlements (YYYY-MM-DD format)
Filter settlements by subaccount ID
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_LIST_SUBACCOUNTSTool to fetch all collection subaccounts. Use when you need to retrieve the complete list of subaccounts for split disbursements.
Input parameters
Page number for pagination (>= 1)
Number of records per page (>= 1)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_LIST_TRANSFERSTool to fetch a list of bulk transfers from your Flutterwave account. Use when you need to retrieve transfer history, check transfer statuses, or filter transfers by reference or status.
Input parameters
Page number to fetch (>= 1). Used for pagination.
Filter transfers by status (e.g., 'successful', 'failed', 'pending', 'new')
Filter transfers by reference. Use this to find a specific transfer by its reference.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_RESOLVE_BANK_ACCOUNTTool to verify and resolve bank account details. Use when you need to retrieve the account holder name for a Nigerian bank account by providing the account number and bank code.
Input parameters
Bank code for the account. Retrieve valid codes via the get banks endpoint. Example: '044' for Access Bank.
Bank account number to resolve. Example: '0690000034'
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_RESOLVE_CARD_BINTool to resolve and retrieve card BIN information from Flutterwave. Use when you need to get issuer details, card type, and country information for a 6-digit BIN.
Input parameters
6-digit Bank Identification Number (BIN) to resolve. The BIN is the first 6 digits of a card number.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_UPDATE_PAYMENT_PLANTool to update an existing payment plan. Use when you need to modify a payment plan's name or status.
Input parameters
The unique identifier of the payment plan to update.
The new name for the payment plan. If provided, updates the plan name.
The new status for the payment plan. Common values include 'active' or 'cancelled'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_UPDATE_SUBACCOUNTTool to update an existing subaccount. Use when you need to modify split disbursement settings or business details.
Input parameters
The numeric ID of the subaccount to update (e.g., from the 'id' field returned when creating a subaccount, not the 'subaccount_id' field which starts with RS_)
Updated split type: 'percentage' or 'flat'
Updated split value for disbursement. For 'percentage' type, use the percentage value (e.g., '10' for 10%). For 'flat' type, use the actual amount in the local currency (e.g., '250'). Pass as string to match API expectations.
Updated bank ISO code for the subaccount
Updated business name for the subaccount
Updated bank account number for the subaccount
Updated business email address
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_VALIDATE_BILL_ITEMTool to validate a bill service before payment. Use before initiating a bill payment to confirm the customer identifier (account number, meter number, etc.) is valid and retrieve customer details.
Input parameters
Biller code (e.g., BIL119 for DSTV in test mode)
Customer identifier to validate (e.g., account number, meter number, or phone number)
Product/item code to validate (e.g., CB141 for DSTV in test mode)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_VERIFY_TRANSACTION_BY_REFERENCETool to verify a transaction using its transaction reference. Use when you have a transaction reference (tx_ref) and need to confirm the transaction status and retrieve its details.
Input parameters
Transaction reference to verify. This is the unique reference provided during transaction initiation.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FLUTTERWAVE_VIEW_TRANSACTION_TIMELINETool to retrieve the event timeline for a transaction. Use after obtaining the transaction ID to audit or track the sequence of events.
Input parameters
Unique identifier of the transaction to retrieve its event timeline (>=1).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 43 agents privately built on Nagent that already use Flutterwave.
Build on Nagent
Connect Flutterwave to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Flutterwave, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Flutterwave is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Flutterwave is connected, you configure its 53 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Flutterwave steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Flutterwave event fires, the agent kicks off automatically.
Every Flutterwave action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Flutterwave ships with 53 pre-built payment processing actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Flutterwave together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Flutterwave-based workflows tailored to your business.