Finmo provides payment collection, payouts, wallets, foreign exchange, virtual accounts, and transaction management for businesses.
Create a real production Finmo customer profile containing personal or company identity data. This stores PII, mutates production, and may start identity-verification or other compliance workflows, but does not itself move money. Confirm that the customer has authorized this processing and supply the organization-specific documented fields. Use a unique idempotency_key and reuse it only for an identical retry.
Create a real production payin that can collect money from a customer and credit a customer or merchant wallet. This has real financial effects. First call FINMO_LIST_PAYIN_METHODS and FINMO_GET_PAYIN_METHOD_REQUIREMENTS, then supply exactly the selected method's required parameters. Reuse the same idempotency_key only for an identical retry within 8 days. A 499 or 504 may mean Finmo already processed the payment: do not blindly retry; check the payin or transaction state with the same merchant reference, or contact Finmo.
Send real production funds from a Finmo wallet to a beneficiary. This reserves and can irreversibly transfer money. First call FINMO_LIST_PAYOUT_METHODS and FINMO_GET_PAYOUT_METHOD_REQUIREMENTS, verify the beneficiary and available wallet balance, and obtain approval for the exact destination and amount. Use a unique idempotency_key and reuse it only for an identical retry within 8 days. Supply either stored tokens or the documented inline sender and beneficiary data. Cross-currency payouts require a matching Finmo fx_rate_id. A 499 or 504 may mean Finmo already processed the payout: never retry blindly; check payout or transaction state using the merchant reference, or contact Finmo.
Create a real payout beneficiary in the connected Finmo production account. This does not move money, but Finmo stores the supplied sensitive bank, proxy, identity, and contact data and the record can enable later payouts. First call FINMO_LIST_PAYOUT_METHODS and FINMO_GET_PAYOUT_METHOD_REQUIREMENTS, then provide only the selected method's required destination and identity fields. A newly created beneficiary may take 24 hours to activate. Reuse idempotency_key only for an identical retry.
Issue a real production full refund for a completed Finmo payin. This moves real money, debits or holds funds in the payin wallet, may incur fees, and may be irreversible. Before calling, verify the payin is refundable and that the full refund is intended. Use a unique idempotency_key and reuse it only for an identical retry within 8 days.
Return the dynamic required fields, validation regexes, limits, instructions, and capabilities for one Finmo payin method. Call this immediately before constructing a payin request.
Get one payin, payout, or refund by its Finmo reference ID. Use this after an ambiguous timeout before retrying a money-moving request with the same idempotency key.
Return the dynamic payout, beneficiary, and sender field requirements for one Finmo payout method. Use it before creating a beneficiary or moving money.
Get one wallet and its currency accounts, including actual and available balances. Reading balances is sensitive but does not move funds.
List one page of individual or company customer profiles and wallet-readiness state. Returns a continuation cursor when more customers are available.
List one page of enabled ways to collect money for a country and currency, with a continuation cursor when more results exist. Use FINMO_GET_PAYIN_METHOD_REQUIREMENTS before creating a payin because required fields vary by method.
List inbound payment attempts with status, method, customer, wallet, and time filters. Returns one page and a continuation cursor.
List one page of stored payout beneficiaries and their destination details. Returns a continuation cursor when more beneficiaries are available; use payout method discovery to assess rail suitability.
List one page of enabled payout rails for a sender and beneficiary country/currency pair. Results may use wildcard sender values. Inspect the returned beneficiary requirements, then call FINMO_GET_PAYOUT_METHOD_REQUIREMENTS for current beneficiary and sender fields before creating a payout or beneficiary. Returns a continuation cursor when more methods are available.
List one page of outbound payments with status, payout method, and time filters. Returns a continuation cursor when more payouts are available.
List one page of refunds with status, originating payin, amount, and time filters. Returns a continuation cursor when more refunds are available.
List organization-level financial transactions for reconciliation, filtered by customer, event type, settlement, reconciliation, or time. Returns one page and a continuation cursor.
List one page of Finmo wallets available to the connected organization or a customer. Returns a continuation cursor when more wallets are available. Summaries exclude balances; use FINMO_GET_WALLET for wallet accounts and balances.
Move real production funds immediately between two Finmo wallets. This money-moving operation may be irreversible. Before calling, use FINMO_GET_WALLET on both wallets to verify the exact destination, active currency accounts, and sufficient source available balance for the amount and currency. Use a unique idempotency_key and reuse it only for an identical retry within 8 days. After an ambiguous failure, check transfer and transaction state before retrying.
The Finmo integration connects your Dench AI CRM directly to Finmo, so agents can read and act on your Finmo data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
19 actions are available for agents to invoke on your behalf. Every call runs through Finmo's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Finmo and click Connect — you'll authorize access through Finmo's own sign-in flow. No API keys or code required.
Ask an agent to use Finmo in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Finmo integration connects your AI CRM to Finmo, so AI agents can work with your Finmo data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Finmo integration currently exposes 19 actions, including Create Customer, Create Payin, Create Payout, Create Payout Beneficiary, Create Refund, and Get Payin Method Requirements. Agents invoke them on your behalf from chat or from automations.
No. You connect Finmo from your Dench workspace using Finmo's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Finmo's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Finmo connection from your workspace settings at any time.