Can I use Dwolla as a CLI?

Yes. KosmoKrator exposes a Dwolla CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Dwolla through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Dwolla tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Dwolla credentials stored?

Dwolla credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Dwolla MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

data

Dwolla MCP, CLI, and Lua Integration for AI Agents

Dwolla integration docs for AI agents: MCP gateway setup, Dwolla CLI commands, Lua API reference, credentials, and function schemas.

Dwolla for agents

Credentials can be configured manually in web or CLI hosts.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Agent Surfaces

Dwolla CLIHeadless setup, JSON output, direct function calls. Dwolla MCPExpose selected tools to local MCP clients. Dwolla LuaAgent-facing namespace and Lua reference. FeedbackReport missing tools, auth issues, or bad metadata.

Machine-Readable Metadata

integration_slug: dwolla
route_slug: dwolla
package: dwolla
auth_strategy: oauth_client_credentials
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true

Function Catalog

Function	Type	Parameters	Description
`dwolla.dwolla_create_application_access_token`	Write `write`	1	Generate an application access token using OAuth 2.0 client credentials flow for server-to-server authentication. Requires client ID and secret sent via Basic authentication header with grant_type=client_credentials in the request body. Returns a bearer access token with expiration time for authenticating API requests scoped to your application. Essential for secure API access. Official Dwolla endpoint: POST /token.
`dwolla.dwolla_get_root`	Read `read`	1	Retrieve the API root entry point to discover available resources and endpoints based on your OAuth access token permissions. Returns HAL+JSON with navigation links to accessible resources including accounts, customers, events, and webhook subscriptions depending on token scope. Essential for API exploration, dynamic resource discovery, and building adaptive client applications that respond to available permissions. Official Dwolla endpoint: GET /.
`dwolla.dwolla_get_account`	Read `read`	2	Returns basic account information for your authorized Main Dwolla Account, including account ID, name, and links to related resources such as funding sources, transfers, and customers. Official Dwolla endpoint: GET /accounts/{id}.
`dwolla.dwolla_create_funding_source`	Write `write`	2	Create a funding source by adding a bank account to a Main Dwolla Account. This endpoint allows you to connect a checking or savings account using either manual bank account details or an exchange resource. For more information about funding sources, see the [Funding Sources API Reference](https://developers.dwolla.com/docs/api-reference/funding-sources). Official Dwolla endpoint: POST /funding-sources.
`dwolla.dwolla_list_funding_sources`	Read `read`	3	Get a list of all funding sources associated with a specific Main Dwolla Account. This endpoint returns both bank accounts and balance funding sources, with detailed information about each funding source's status, type, and available processing channels. Official Dwolla endpoint: GET /accounts/{id}/funding-sources.
`dwolla.dwolla_list_and_search_transfers`	Read `read`	11	Returns a paginated, searchable list of transfers associated with the specified Main Dwolla account. Supports advanced filtering by amount range, date range, transfer status, and correlation ID. Results are limited to 10,000 transfers per query; use date range filters for historical data beyond this limit. Official Dwolla endpoint: GET /accounts/{id}/transfers.
`dwolla.dwolla_list_mass_payments`	Read `read`	5	Returns a paginated list of mass payments created by your Main Dwolla account. Results are sorted by creation date in descending order (newest first) and can be filtered by correlation ID. Official Dwolla endpoint: GET /accounts/{id}/mass-payments.
`dwolla.dwolla_list_and_search_customers`	Read `read`	5	Returns a paginated list of customers sorted by creation date. Supports fuzzy search across customer names, business names, and email addresses, plus exact filtering by email and verification status. Default limit is 25 customers per page, maximum 200. Official Dwolla endpoint: GET /customers.
`dwolla.dwolla_create_customer`	Write `write`	2	Creates a new customer with different verification levels and capabilities. Supports personal verified customers (individuals), business verified customers (businesses), unverified customers, and receive-only users. Customer type determines transaction limits, verification requirements, and available features. Official Dwolla endpoint: POST /customers.
`dwolla.dwolla_get_customer`	Read `read`	2	Retrieve identifying information for a specific customer. The returned data varies by customer type - verified customers include contact details, address information, and verification status, while unverified customers and receive-only users contain basic contact information only. Official Dwolla endpoint: GET /customers/{id}.
`dwolla.dwolla_update`	Read `read`	3	Update Customer information, upgrade an unverified Customer to a verified Customer, suspend a Customer, deactivate a Customer, reactivate a Customer, and update a verified Customer's information to retry verification. Official Dwolla endpoint: POST /customers/{id}.
`dwolla.dwolla_list_business_classifications`	Read `read`	1	Returns a directory of business and industry classifications required for creating business verified customers. Each business classification contains multiple industry classifications. The industry classification ID must be provided in the businessClassification parameter during business customer creation for verification. Official Dwolla endpoint: GET /business-classifications.
`dwolla.dwolla_retrieve_business_classification`	Read `read`	2	Returns a specific business classification with its embedded industry classifications. Use this endpoint to browse available industry options within a business category and obtain the industry classification ID required for the businessClassification parameter when creating business verified customers. Official Dwolla endpoint: GET /business-classifications/{id}.
`dwolla.dwolla_list_beneficial_owners_for_customer`	Read `read`	2	Returns all beneficial owners associated with a business verified customer. Beneficial owners are individuals who directly or indirectly own 25% or more of the company's equity. Includes personal information, verification status, and address details for each owner. Official Dwolla endpoint: GET /customers/{id}/beneficial-owners.
`dwolla.dwolla_create_beneficial_owner_for_customer`	Write `write`	3	Creates a new beneficial owner for a business verified customer. Beneficial owners are individuals who own 25% or more of the company's equity. Requires personal information, address, and SSN or passport for identity verification. Official Dwolla endpoint: POST /customers/{id}/beneficial-owners.
`dwolla.dwolla_retrieve_beneficial_owner`	Read `read`	2	Returns detailed information for a specific beneficial owner, including personal information, address, and verification status. The verification status indicates the owner's identity verification progress and affects the business customer's transaction capabilities. Official Dwolla endpoint: GET /beneficial-owners/{id}.
`dwolla.dwolla_update_beneficial_owner`	Write `write`	3	Updates a beneficial owner's information to retry verification when their status is "incomplete". Only beneficial owners with incomplete verification status can be updated. Used to correct information that caused initial verification to fail. Official Dwolla endpoint: POST /beneficial-owners/{id}.
`dwolla.dwolla_delete_beneficial_owner`	Write `write`	2	Permanently removes a beneficial owner from a business customer. This action is irreversible and the beneficial owner cannot be retrieved after removal. Removing a beneficial owner will change the customer's certification status to "recertify". Official Dwolla endpoint: DELETE /beneficial-owners/{id}.
`dwolla.dwolla_get_beneficial_ownership_status_for_customer`	Read `read`	2	Returns the certification status of beneficial ownership for a business verified customer. Status indicates whether beneficial owner information has been certified and affects the customer's ability to send funds. Possible values include uncertified, certified, and recertify. Official Dwolla endpoint: GET /customers/{id}/beneficial-ownership.
`dwolla.dwolla_certify_beneficial_ownership_for_customer`	Read `read`	3	Updates the beneficial ownership certification status to "certified", confirming that all beneficial owner information is accurate and complete. This action enables the business customer to send funds and is required to complete the verification process. Official Dwolla endpoint: POST /customers/{id}/beneficial-ownership.
`dwolla.dwolla_list_customer_documents`	Read `read`	2	Returns all identity verification documents submitted for a customer. Includes document status, verification results, document type (passport, driver's license, etc.), and failure reasons if verification was rejected. Used to track document submission and verification progress during the business verification process. Official Dwolla endpoint: GET /customers/{id}/documents.
`dwolla.dwolla_create_customer_document`	Write `write`	3	Uploads an identity verification document for a customer using multipart form-data. Required when a customer has "document" status during the verification process. Official Dwolla endpoint: POST /customers/{id}/documents.
`dwolla.dwolla_list_beneficial_owner_documents`	Read `read`	2	Returns all identity verification documents submitted for a beneficial owner. Includes document status, verification results, document type (passport, driver's license, etc.), and failure reasons if verification was rejected. Used to track document submission and verification progress during the business verification process. Official Dwolla endpoint: GET /beneficial-owners/{id}/documents.
`dwolla.dwolla_create_beneficial_owner_document`	Write `write`	3	Uploads an identity verification document for a beneficial owner using multipart form-data. Required when a beneficial owner has "document" status during the business verification process. Official Dwolla endpoint: POST /beneficial-owners/{id}/documents.
`dwolla.dwolla_retrieve_document`	Read `read`	2	Returns detailed information about a specific identity verification document, including its status, type, and verification results. Used to track document submission and verification progress during the business verification process. Official Dwolla endpoint: GET /documents/{id}.
`dwolla.dwolla_initiate_kba_for_customer`	Read `read`	3	Creates a new KBA (Knowledge-Based Authentication) session for a personal Verified Customer. Returns a KBA identifier that represents the session and is used to retrieve authentication questions for customer verification. Official Dwolla endpoint: POST /customers/{id}/kba.
`dwolla.dwolla_get_kba_questions`	Read `read`	2	Returns the KBA questions for a specific KBA session. The questions are used to verify the customer's identity during the KBA process. Official Dwolla endpoint: GET /kba/{id}.
`dwolla.dwolla_verify_kba_questions`	Write `write`	3	Submits customer answers to KBA questions for identity verification. Requires four question-answer pairs with questionId and answerId values. Returns verification status indicating whether the customer passed or failed the KBA authentication. Official Dwolla endpoint: POST /kba/{id}.
`dwolla.dwolla_list_customer_funding_sources`	Read `read`	3	Returns all funding sources for a customer, including bank accounts, debit card funding sources, and Dwolla balance (verified customers only). Shows verification status, limited account details, and creation dates. Card funding sources include masked card information. Supports filtering to exclude removed funding sources using the removed parameter. Official Dwolla endpoint: GET /customers/{id}/funding-sources.
`dwolla.dwolla_create_customer_funding_source`	Write `write`	3	Creates a bank account or debit card funding source for a customer. Supports multiple methods including manual entry with routing/account numbers, instant verification using existing open banking connections, debit card addition via Exchange, and virtual account numbers. Bank funding sources require verification before transfers can be initiated. Official Dwolla endpoint: POST /customers/{id}/funding-sources.
`dwolla.dwolla_get_funding_source`	Read `read`	2	Returns detailed information for a specific funding source, including its type, status, and verification details. Supports bank accounts (via Open Banking), debit card funding sources, and Dwolla balance (verified customers only). Debit card funding sources include masked card details such as brand, last four digits, expiration date, and cardholder name. Official Dwolla endpoint: GET /funding-sources/{id}.
`dwolla.dwolla_update_or_remove_funding_source`	Write `write`	3	Updates a bank funding source's details or soft deletes it. When updating, you can change the name (any status) or modify routing/account numbers and account type (unverified status only). When removing, the funding source is soft deleted and can still be accessed but marked as removed. Official Dwolla endpoint: POST /funding-sources/{id}.
`dwolla.dwolla_get_micro_deposits`	Read `read`	2	Returns the status and details of micro-deposits for a funding source to check verification eligibility. Includes deposit status (pending, processed, failed), creation timestamp, and failure details with ACH return codes if deposits failed. Use this endpoint to determine when micro-deposits are ready for verification. Official Dwolla endpoint: GET /funding-sources/{id}/micro-deposits.
`dwolla.dwolla_initiate_or_verify_micro_deposits`	Write `write`	3	Handles micro-deposit bank verification process. Make a request without a request body to initiate two small deposits to the customer's bank account. Include deposit amounts to verify the received values and complete verification. Official Dwolla endpoint: POST /funding-sources/{id}/micro-deposits.
`dwolla.dwolla_get_funding_source_balance`	Read `read`	2	Returns the current balance for a specific funding source. For bank accounts, includes available and closing balances; for Dwolla balance, includes balance and total amounts; for settlement accounts (bankUsageType = card-network), includes available balance only. Supports bank accounts (via Open Banking), Dwolla balance (verified customers only), and settlement accounts for card network processing. Official Dwolla endpoint: GET /funding-sources/{id}/balance.
`dwolla.dwolla_get_van_routing`	Read `read`	2	Returns the unique account and routing numbers for a Virtual Account Number (VAN) funding source. These numbers can be used by external systems to initiate ACH transactions that pull funds from or push funds to the associated Dwolla balance. Official Dwolla endpoint: GET /funding-sources/{id}/ach-routing.
`dwolla.dwolla_create_on_demand_transfer_authorization`	Write `write`	2	Create an on-demand transfer authorization that allows Customers to pre-authorize variable amount ACH transfers from their bank account for future payments. This authorization is used when creating Customer funding sources to enable flexible payment processing. Returns UI text elements including authorization body text and button text for display in your application's bank account addition flow. Official Dwolla endpoint: POST /on-demand-authorizations.
`dwolla.dwolla_initiate_transfer`	Read `read`	3	Initiate a transfer Official Dwolla endpoint: POST /transfers.
`dwolla.dwolla_get_transfer`	Read `read`	2	Retrieve a transfer Official Dwolla endpoint: GET /transfers/{id}.
`dwolla.dwolla_cancel_transfer`	Write `write`	3	Cancel a pending transfer by setting its status to cancelled. Only transfers in pending status can be cancelled before processing begins. Returns the updated transfer resource with cancelled status. Use this endpoint to stop a bank transfer from further processing. Official Dwolla endpoint: POST /transfers/{id}.
`dwolla.dwolla_list_customer_transfers`	Read `read`	11	List and search transfers for a customer Official Dwolla endpoint: GET /customers/{id}/transfers.
`dwolla.dwolla_list_transfer_fees`	Read `read`	2	Retrieve detailed fee information for a specific transfer by its unique identifier. Returns the total number of fees and individual fee transaction details including amounts, status, and links to source and destination accounts. Official Dwolla endpoint: GET /transfers/{id}/fees.
`dwolla.dwolla_get_transfer_failure_reason`	Read `read`	2	Retrieve a transfer failure reason Official Dwolla endpoint: GET /transfers/{id}/failure.
`dwolla.dwolla_initiate_mass_payment`	Read `read`	3	Create a mass payment containing up to 5,000 individual payment items from a Dwolla Main Account or Verified Customer funding source. Supports optional metadata, correlation IDs for traceability, deferred processing, and expedited transfer options including same-day ACH clearing. Returns the location of the created mass payment resource with a unique identifier for tracking and management. Official Dwolla endpoint: POST /mass-payments.
`dwolla.dwolla_get_mass_payment`	Read `read`	2	Retrieve detailed information for a mass payment by its unique identifier. Returns the current processing status (pending, processing, or complete), creation date, metadata, and links to the source funding source and payment items. Use this endpoint to monitor mass payment processing progress and determine when to check individual item results. Official Dwolla endpoint: GET /mass-payments/{id}.
`dwolla.dwolla_update_mass_payment`	Write `write`	3	Update the status of a deferred mass payment to control its processing lifecycle. Set status to `pending` to trigger processing and begin fund transfers, or `cancelled` to permanently cancel the mass payment before processing begins. Only applies to mass payments created with deferred status. Returns the updated mass payment resource with the new status. Official Dwolla endpoint: POST /mass-payments/{id}.
`dwolla.dwolla_list_mass_payment_items`	Read `read`	5	Retrieve individual payment items within a mass payment with optional status filtering and pagination support. Each item represents a distinct payment with status indicators (failed, pending, success) showing whether a transfer was successfully created. Returns paginated item details including amount, destination, metadata, and error information for failed items. Supports filtering by status and standard pagination. Official Dwolla endpoint: GET /mass-payments/{id}/items.
`dwolla.dwolla_get_mass_payment_item`	Read `read`	2	Retrieve detailed information for a specific mass payment item by its unique identifier. Returns item status, amount, metadata, and links to the parent mass payment, associated transfer, and destination funding source. Use this endpoint to check the processing status and details of an individual item within a mass payment batch. Official Dwolla endpoint: GET /mass-payment-items/{itemId}.
`dwolla.dwolla_list_customer_mass_payments`	Read `read`	5	List mass payments for customer Official Dwolla endpoint: GET /customers/{id}/mass-payments.
`dwolla.dwolla_get_label`	Read `read`	2	Retrieve details for a specific Label used to categorize and track funds within your account. Returns Label information including unique identifier, current amount with currency, and creation timestamp. Official Dwolla endpoint: GET /labels/{id}.
`dwolla.dwolla_remove_label`	Write `write`	2	Delete a Label to stop tracking funds and remove it from your account. Returns success status if the Label is successfully removed. Use this to streamline your account management and remove unused Labels from your system. Official Dwolla endpoint: DELETE /labels/{id}.
`dwolla.dwolla_list_customer_labels`	Read `read`	4	Returns all labels for a specified Verified Customer, sorted by creation date (most recent first). Supports pagination with limit and offset parameters. Each label includes its current amount and creation timestamp. Official Dwolla endpoint: GET /customers/{id}/labels.
`dwolla.dwolla_create_customer_label`	Write `write`	3	Creates a new label for a Verified Customer with a specified amount. Labels help organize and track funds within a customer's balance. Returns the location of the created label resource in the response header. Official Dwolla endpoint: POST /customers/{id}/labels.
`dwolla.dwolla_list_label_ledger_entries`	Read `read`	4	Returns all ledger entries for a specific Label, sorted by creation date (newest first). Supports pagination with limit and offset parameters. Each ledger entry includes its amount, currency, and creation timestamp. Official Dwolla endpoint: GET /labels/{id}/ledger-entries.
`dwolla.dwolla_create_label_ledger_entry`	Write `write`	3	Create a new ledger entry to track fund adjustments on a Label by specifying a positive or negative amount value. Returns the location of the created ledger entry in the response header. Label amounts cannot go negative, so validation errors occur if the entry would result in a negative Label balance. Official Dwolla endpoint: POST /labels/{id}/ledger-entries.
`dwolla.dwolla_get_label_ledger_entry`	Read `read`	2	Returns detailed information for a specific ledger entry on a Label, including its amount, currency, and creation timestamp. Official Dwolla endpoint: GET /ledger-entries/{ledgerEntryId}.
`dwolla.dwolla_create_label_reallocation`	Write `write`	2	Reallocates funds between two labels belonging to the same Verified Customer. Moves the specified amount from the source label to the destination label, creating ledger entries for both. The reallocation only succeeds if the source label has sufficient funds. Official Dwolla endpoint: POST /label-reallocations.
`dwolla.dwolla_retrieve_label_reallocation`	Read `read`	2	Retrieve details for a specific label reallocation that transfers funds between Labels. Returns reallocation information including source and destination Labels, amount transferred, status, and creation timestamp. Use this to track and audit fund movements between different Labels. Official Dwolla endpoint: GET /label-reallocations/{reallocationId}.
`dwolla.dwolla_list_events`	Read `read`	3	Returns a paginated list of events representing state changes to resources in your Dwolla application. Events track actions on customers, transfers, funding sources, and other resources, sorted by creation date (newest first). Events are retained for 30 days and are essential for webhook notifications and system activity monitoring. Official Dwolla endpoint: GET /events.
`dwolla.dwolla_get_event`	Read `read`	2	Returns detailed information for a specific event representing a state change that occurred on a resource in your Dwolla application. Includes the event topic, timestamp, resource links, and correlation ID if applicable. Official Dwolla endpoint: GET /events/{id}.
`dwolla.dwolla_list_webhook_subscriptions`	Read `read`	1	Retrieve all webhook subscriptions that belong to an application including their configuration details and status. Returns subscription details including webhook endpoints, status, creation dates, and links to associated webhooks with total count. Essential for webhook management and monitoring subscription health. Official Dwolla endpoint: GET /webhook-subscriptions.
`dwolla.dwolla_create_webhook_subscription`	Write `write`	2	Create a webhook subscription to deliver webhook notifications to a specified URL endpoint for your application. Requires a destination URL where Dwolla will send notifications and a secret key for webhook validation and security. Returns the location of the created subscription resource. Essential for establishing real-time event notifications and automated integrations with Dwolla's payment processing events. Official Dwolla endpoint: POST /webhook-subscriptions.
`dwolla.dwolla_get_webhook_subscription`	Read `read`	2	Retrieve detailed information for a specific webhook subscription by its unique identifier. Returns subscription configuration including URL endpoint, creation date, and links to associated webhooks for comprehensive subscription management. Essential for monitoring webhook subscription status and accessing webhook delivery history. Official Dwolla endpoint: GET /webhook-subscriptions/{id}.
`dwolla.dwolla_update_webhook_subscription`	Write `write`	3	Update a webhook subscription to pause or resume webhook delivery notifications. Allows toggling the paused status to temporarily stop webhook notifications without deleting the subscription. Returns the updated subscription resource with the new paused status. Use this endpoint to manage webhook delivery during maintenance or troubleshooting periods. Official Dwolla endpoint: POST /webhook-subscriptions/{id}.
`dwolla.dwolla_delete`	Read `read`	2	Delete a webhook subscription to permanently remove webhook notifications for your application. This action stops all future webhook deliveries and cannot be undone. Returns the deleted subscription resource for confirmation. Use this endpoint when webhook notifications are no longer needed or when cleaning up unused subscriptions. Official Dwolla endpoint: DELETE /webhook-subscriptions/{id}.
`dwolla.dwolla_list_webhooks`	Read `read`	6	List webhooks for a webhook subscription Official Dwolla endpoint: GET /webhook-subscriptions/{id}/webhooks.
`dwolla.dwolla_get_webhook`	Read `read`	2	Retrieve detailed information for a specific webhook by its unique identifier including delivery attempts and response data. Returns webhook details with topic, account information, delivery attempts containing request/response history, and links to subscription and retry resources. Essential for debugging webhook delivery issues, analyzing response data, and monitoring notification processing status. Official Dwolla endpoint: GET /webhooks/{id}.
`dwolla.dwolla_list_webhook_retries`	Read `read`	2	Retrieve all retry attempts for a specific webhook including timestamps and delivery details. Returns a list of retry attempts with unique identifiers, timestamps, and links to the parent webhook with total count. Essential for tracking webhook delivery failures, analyzing retry patterns, and debugging webhook notification issues to ensure reliable event processing. Official Dwolla endpoint: GET /webhooks/{id}/retries.
`dwolla.dwolla_retry_webhook`	Read `read`	3	Retry a webhook by its unique identifier to redeliver the notification to your endpoint. Creates a new retry attempt and returns the location of the new webhook resource. Essential for recovering from webhook delivery failures and ensuring reliable event notification processing in your application. Official Dwolla endpoint: POST /webhooks/{id}/retries.
`dwolla.dwolla_simulate_bank_transfer_processing`	Read `read`	2	Sandbox simulations (bank transfers, VAN transfers, or customer verification directives) Official Dwolla endpoint: POST /sandbox-simulations.
`dwolla.dwolla_list_exchange_partners`	Read `read`	1	Returns a list of all supported exchange partners. Each partner includes a unique ID, name, and status indicating whether they are active or inactive. Official Dwolla endpoint: GET /exchange-partners.
`dwolla.dwolla_get_exchange_partner`	Read `read`	2	Returns details for a specific open banking provider that integrates with Dwolla. Includes partner name, status, and creation date. Use this to verify partner availability before creating exchanges and funding sources. Official Dwolla endpoint: GET /exchange-partners/{id}.
`dwolla.dwolla_list_account_exchanges`	Read `read`	1	Returns all exchanges for your Dwolla account. Exchanges represent connections between external bank accounts and your account through open banking partners. Includes exchange status, creation date, and associated partner information. Official Dwolla endpoint: GET /exchanges.
`dwolla.dwolla_create_account_exchange`	Write `write`	1	Create an exchange for an account. The request body will vary based on the exchange partner. For Finicity, the request body will include finicity-specific fields. For MX Secure Exchange, the request body will include a token. For Flinks Secure Exchange, the request body will include a token. For Plaid Secure Exchange, the request body will include a token. Official Dwolla endpoint: POST /exchanges.
`dwolla.dwolla_get_exchange`	Read `read`	2	Returns details for a specific exchange connection between Dwolla and an open banking partner for a customer's bank account. Includes exchange status, creation date, and links to the associated customer and exchange partner. Official Dwolla endpoint: GET /exchanges/{id}.
`dwolla.dwolla_list_customer_exchanges`	Read `read`	2	Returns all exchanges for a specific customer. Exchanges represent connections between the customer's external bank accounts and open banking partners. Includes exchange status, creation date, and links to associated funding sources and partners. Official Dwolla endpoint: GET /customers/{id}/exchanges.
`dwolla.dwolla_create_customer_exchange`	Write `write`	3	Creates an exchange connection between a customer and Dwolla. Request body varies by partner (Plaid, MX, Flinks, Finicity, Checkout.com). For bank accounts, use Plaid, MX, Flinks, or Finicity to establish secure access to the customer's bank account data. For debit cards (Push to Card), use Checkout.com and pass the payment ID from Checkout.com Flow. Official Dwolla endpoint: POST /customers/{id}/exchanges.
`dwolla.dwolla_create_customer_exchange_session`	Write `write`	3	Creates an exchange session for a customer. Use cases include: - Plaid / MX: Instant bank account verification (open banking). For faster verification as compared to traditional micro-deposits. - Checkout.com: Debit card capture for Push to Card. Create a session, then retrieve it to get `externalProviderSessionData` (payment session) for the Checkout.com Flow component. Official Dwolla endpoint: POST /customers/{id}/exchange-sessions.
`dwolla.dwolla_retrieve_customer_exchange_session`	Read `read`	2	Retrieve exchange session Official Dwolla endpoint: GET /exchange-sessions/{id}.
`dwolla.dwolla_create_re_auth_exchange_session`	Write `write`	3	Creates a re-authentication exchange session to refresh a user's bank account connection when their existing authorization is no longer valid. Required when receiving an UpdateCredentials error during bank balance checks or when user re-authentication is needed. Official Dwolla endpoint: POST /exchanges/{id}/exchange-sessions.
`dwolla.dwolla_list_available_exchange_connections`	Read `read`	2	Returns available exchange connections for a customer's bank accounts authorized through MX Connect. Each connection includes an account name and availableConnectionToken required to create exchanges and funding sources for transfers. Official Dwolla endpoint: GET /customers/{id}/available-exchange-connections.
`dwolla.dwolla_create_client_token`	Write `write`	2	Create a client token Official Dwolla endpoint: POST /client-tokens.