Skip to content
J·BJon BishopFractional growth marketer

Business platforms · llms.txt file breakdown

Dwolla llms.txt

A directly retrieved Markdown index for Dwolla's documentation, with 154 links across 3 detected headings.

The actual file

Source Markdown

The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.

Open saved text ↗

Showing the first 18000 characters. Load the complete file to read the remainder.

# Dwolla Developer Portal

> Comprehensive guides, API documentation, SDKs, and tools for building, testing, and launching account-to-account payment integrations with Dwolla.

- [Dwolla Developers](https://developers.dwolla.com/index.md): Build, test, and launch payment solutions with Dwolla's comprehensive API documentation and developer tools.
- [Guides and Concepts](https://developers.dwolla.com/docs.md): Start with foundational concepts, move into quickstarts and use cases, and keep API reference and SDKs close at hand when you need them.
- [Quickstart](https://developers.dwolla.com/docs/quickstart.md): Make your first authenticated Dwolla API call in under 5 minutes.
- [What is Dwolla?](https://developers.dwolla.com/docs/what-is-dwolla.md): Leverage Dwolla's existing financial institution relationship to connect your business to the U.S. banking infrastructure.
- [Customer Types](https://developers.dwolla.com/docs/customer-types.md): Understanding and selecting the appropriate Customer type is the first step to a successful payment integration.
- [Testing in the Sandbox](https://developers.dwolla.com/docs/testing.md): Test and refine your integration in the Dwolla Sandbox—a free, full-featured environment that simulates real API interactions, allowing you to build, experiment, and validate your application before going live.
- [Send Money](https://developers.dwolla.com/docs/send-money.md): Learn the key steps involved with sending funds to your end user's bank account.
- [Receive Money from Users](https://developers.dwolla.com/docs/receive-money.md): Learn the key steps involved with receiving funds from your end user's bank account.
- [Transfer Money Between Users](https://developers.dwolla.com/docs/transfer-money-between-users.md): Facilitate ACH transfers between two distinct parties, e.g. for marketplace applications that connect buyers with sellers for bank to bank payments.
- [Transfer Money Me-to-Me](https://developers.dwolla.com/docs/transfer-money-me-to-me.md): Move funds between two different bank accounts belonging to a single Verified Customer, e.g. for savings applications that move funds between a Customer's checking and savings accounts.
- [Business Verified Customer](https://developers.dwolla.com/docs/business-verified-customer.md): Verifying a business' identity enables increased functionality on the platform. Create a business Customer that can receive funds and send up to $10,000 per transfer (default).
- [Personal Verified Customer](https://developers.dwolla.com/docs/personal-verified-customer.md): Learn how to create a Verified personal Customer that can send and receive funds.
- [Balance Funding Source](https://developers.dwolla.com/docs/balance-funding-source.md): Send to, receive from, or hold funds within the Dwolla network for client master accounts and Verified Customer accounts.
- [Bank Funding Source](https://developers.dwolla.com/docs/bank-funding-source.md): Learn about the different methods of adding and verifying a bank funding source to a Customer account.
- [Virtual Account Numbers](https://developers.dwolla.com/docs/virtual-account-numbers.md): A Virtual Account Number (VAN) provides a dedicated routing path for external transactions to flow into and out of a Dwolla balance. Each VAN generates unique account and routing numbers that enable you to credit or debit a Dwolla balance through ACH transfers.
- [Verify Bank with Micro-deposits](https://developers.dwolla.com/docs/micro-deposit-verification.md): Learn how to verify a user's bank account ownership by initiating micro-deposits - small deposits that are sent to the account and must be verified by the user to confirm account ownership.
- [Transfer Lifecycle](https://developers.dwolla.com/docs/transfer-lifecycle.md): Learn about the complete lifecycle of a transfer in Dwolla and find out what webhooks you can expect to receive during each step.
- [Transfer Processing Times](https://developers.dwolla.com/docs/transfer-processing-times.md): Learn more about transfer clearing times, including `standard` ,`expedited` and `instant` clearing.
- [Transfer Failures](https://developers.dwolla.com/docs/transfer-failures.md): Familiarize yourself with the unhappy path of transfers and build resilient practices to mitigate ACH returns. Learn about returns, why they happen and recommended actions your application can take based on the return code.
- [Same-Day ACH](https://developers.dwolla.com/docs/same-day-ach.md): An overview of Same Day ACH and leveraging next-available processing times for faster transfers.
- [Instant Payments](https://developers.dwolla.com/docs/instant-payments.md): Learn about Instant Payments (defined as both FedNow Service and RTP), and how to identify and send transfers to instant payment-enabled funding sources.
- [Facilitator Fee](https://developers.dwolla.com/docs/facilitator-fee.md): Charge users a flat rate amount to be removed from a payment as a fee. The fee is sent to the creator of the application.
- [Overview](https://developers.dwolla.com/docs/secure-exchange.md): The Secure Exchange solution connects clients with integrated ecosystem partners to seamlessly share data and initiate account-to-account payments.
- [Dwolla + Plaid](https://developers.dwolla.com/docs/secure-exchange/plaid.md): Learn how to integrate Dwolla and Plaid using Dwolla's Secure Token Exchange solution to securely verify and link your users' bank accounts for ACH payments, without handling sensitive account data directly.
- [Overview](https://developers.dwolla.com/docs/open-banking.md): Simplify Open Banking Integration with Dwolla's API. Leverage a single API to connect to various Open Banking providers and streamline account linking, verification, and data retrieval for your application.
- [Plaid: Instant Account Verification](https://developers.dwolla.com/docs/open-banking/plaid.md): Step-by-step guide to integrating Dwolla's Open Banking solution with Plaid. Learn how to enable instant account verification, streamline account-to-account (A2A) payments, and enhance security for enterprise payment workflows.
- [MX: Instant Account Verification](https://developers.dwolla.com/docs/open-banking/mx.md): Step-by-step guide to integrating Dwolla's Open Banking solution with MX. Learn how to enable instant account verification, streamline account-to-account (A2A) payments, and enhance security for enterprise payment workflows.
- [Bank Balance Check](https://developers.dwolla.com/docs/open-banking/bank-balance-check.md): Learn how to use Dwolla's Open Banking Bank Balance Check to verify account balances in real time, reduce payment failures, and improve the success rate of your ACH transactions.
- [Webhook Events](https://developers.dwolla.com/docs/webhook-events.md): Real-time event notifications. Determine why a webhook subscription is vital to the experience of your application.
- [Operational Notifications](https://developers.dwolla.com/docs/operational-notifications.md): Understand what Dwolla events are tied to notifications that are sent to your end users. Preview the customizable email templates here.
- [Working with Webhooks](https://developers.dwolla.com/docs/working-with-webhooks.md): Implement simple, real-time, event notifications regarding account and transaction status, and more.
- [Overview](https://developers.dwolla.com/docs/api-reference.md): Comprehensive, structured, and up-to-date documentation for all Dwolla API endpoints, parameters, request/response schemas, and usage examples.
- [Overview](https://developers.dwolla.com/docs/api-reference/api-fundamentals.md): Streamline A2A Payments with Dwolla: Understand the API Fundamentals. Explore request/response structures, authentication, error handling, and more.
- [Making Requests and Authentication](https://developers.dwolla.com/docs/api-reference/api-fundamentals/making-requests-and-authentication.md): Learn how to construct well-formed API requests, set essential headers, and implement robust authentication.
- [JSON-HAL and Dwolla HAL-Forms](https://developers.dwolla.com/docs/api-reference/api-fundamentals/json-hal-hypermedia.md): Uncover the power of Dwolla HAL-Forms for intuitive API interactions. Grasp JSON-HAL and how Dwolla expands it for dynamic forms. Effortlessly transition between resource states and gain valuable insights for a streamlined integration.
- [Handling Responses](https://developers.dwolla.com/docs/api-reference/api-fundamentals/handling-responses.md): Learn how to interpret Dwolla API responses including response types, status codes, headers, and body conventions.
- [Handling Errors](https://developers.dwolla.com/docs/api-reference/api-fundamentals/errors.md): Dwolla API Errors: Master Error Handling. Grasp standard HTTP status codes, Dwolla error codes, and embedded errors.
- [Rate Limits](https://developers.dwolla.com/docs/api-reference/api-fundamentals/rate-limits.md): Ensure smooth integration by understanding Dwolla's API rate limits. Grasp concurrency and volume-based limits, and learn effective strategies to handle 429 Too Many Requests errors.
- [Idempotency Key](https://developers.dwolla.com/docs/api-reference/api-fundamentals/idempotency-key.md): Generate unique keys to prevent accidental duplicate transactions and ensure predictable API behavior. Build robust and reliable financial applications with confidence.
- [IP Allowlist](https://developers.dwolla.com/docs/api-reference/api-fundamentals/ip-allowlist.md): Understand IP Allowlisting. Explore how to define authorized IP addresses, prevent unauthorized activity, and troubleshoot Forbidden errors.
- [Debugging with X-Request-ID](https://developers.dwolla.com/docs/api-reference/api-fundamentals/debugging.md): Troubleshoot API Request Issues. Discover efficient methods to identify and resolve request errors.
- [root](https://developers.dwolla.com/docs/api-reference/root.md): 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 ex…
- [Create an application access token](https://developers.dwolla.com/docs/api-reference/tokens/create-an-application-access-token.md): 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 authenti…
- [Overview](https://developers.dwolla.com/docs/api-reference/accounts.md): Endpoints for your Main Dwolla account that include funding source creation, mass payment and transfer listings, and retrieving account details.
- [Retrieve account details](https://developers.dwolla.com/docs/api-reference/accounts/retrieve-account-details.md): 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.
- [Create a funding source for an account](https://developers.dwolla.com/docs/api-reference/accounts/create-a-funding-source-for-an-account.md): 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.
- [List funding sources for an account](https://developers.dwolla.com/docs/api-reference/accounts/list-funding-sources-for-an-account.md): 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.
- [List and search account transfers](https://developers.dwolla.com/docs/api-reference/accounts/list-and-search-transfers-for-an-account.md): 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…
- [List account mass payments](https://developers.dwolla.com/docs/api-reference/accounts/list-mass-payments-for-an-account.md): 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.
- [Overview](https://developers.dwolla.com/docs/api-reference/customers.md): Create, search and update Customers, and search for business-classification.
- [List and search customers](https://developers.dwolla.com/docs/api-reference/customers/list-and-search-customers.md): 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.
- [Create a customer](https://developers.dwolla.com/docs/api-reference/customers/create-a-customer.md): 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 availabl…
- [Retrieve a customer](https://developers.dwolla.com/docs/api-reference/customers/retrieve-a-customer.md): 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.
- [Update a customer](https://developers.dwolla.com/docs/api-reference/customers/update-a-customer.md): 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.
- [List business classifications](https://developers.dwolla.com/docs/api-reference/customers/list-business-classifications.md): 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 cr…
- [Retrieve a business classification](https://developers.dwolla.com/docs/api-reference/customers/retrieve-a-business-classification.md): 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 custome…
- [Overview](https://developers.dwolla.com/docs/api-reference/kba.md): Apply Knowledge Based Authentication (KBA) in your application to verify the identity of a Personal Verified Customer.
- [Initiate a KBA session](https://developers.dwolla.com/docs/api-reference/kba/initiate-a-kba-session.md): 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.
- [Retrieve KBA Questions](https://developers.dwolla.com/docs/api-reference/kba/retrieve-kba-questions.md): Returns the KBA questions for a specific KBA session. The questions are used to verify the customer's identity during the KBA process.
- [Verify KBA Questions](https://developers.dwolla.com/docs/api-reference/kba/verify-kba-questions.md): 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.
- [Overview](https://developers.dwolla.com/docs/api-reference/beneficial-owners.md): Create, certify, remove, update and list Beneficial Owners for a Business Verified Customer.
- [List customer beneficial owners](https://developers.dwolla.com/docs/api-reference/beneficial-owners/list-beneficial-owners.md): 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.
- [Create customer beneficial owner](https://developers.dwolla.com/docs/api-reference/beneficial-owners/create-beneficial-owner.md): 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.
- [Retrieve beneficial owner](https://developers.dwolla.com/docs/api-reference/beneficial-owners/retrieve-beneficial-owner.md): 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.
- [Update beneficial owner](https://developers.dwolla.com/docs/api-reference/beneficial-owners/update-beneficial-owner.md): 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.
- [Rem

Measured from the saved file

Linked document

UTF-8 text size
45.4 KB46526 bytes
Token count
8919o200k_base encoding
Markdown links
154154 distinct URLs
Fenced code blocks
0166 lines in the file

Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.

Project H1
Dwolla Developer Portal

Opening blockquote

Comprehensive guides, API documentation, SDKs, and tools for building, testing, and launching account-to-account payment integrations with Dwolla.

Context architecture

How the content is divided

2 H2 sections organize 154 parsed Markdown links. 150 links point to .md or .markdown paths; 4 link occurrences use another hostname. Linked destinations have not been recursively validated.

H2 sectionLinksUTF-8 bytesTokens
OpenAPI SpecsLine 15619928
OptionalLine 160 · Optional319647

Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.

Embedded material

Code, installation and API examples

Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
2 links have authentication-related labels

Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.

Publisher prioritization

The Optional section

1 H2 section named “Optional” contain 3 parsed links. 151 links sit outside those sections. That puts 1.9% of the file’s parsed links under Optional.

The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.

Machine-readable routes

MCP references and configuration text

MCP-related text was detected in the captured file. 1 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.

These are text and link observations. No MCP server connection, authentication or tool call was tested.

Index and bundle

llms-full.txt companion

Verified text companion

Text companion verified

https://developers.dwolla.com/llms-full.txt ↗
Discovery
Conventional sibling path checked
HTTP response
200 · text/plain; charset=utf-8
Text size
955.3 KB · 978196 bytes (measured)
Token count
242340 o200k_base tokens
Retrieval scope
Complete body retrieved

A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.

Change evidence

What can be said about freshness

This capture establishes a baseline. Update frequency cannot be determined from one observation.

Linked release and migration material

1 links have release, changelog, deprecation or migration terms in their labels or paths. These provide places to investigate product changes separately.

File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.

Capture identity and measurement method
Requested endpoint
https://developers.dwolla.com/llms.txt
Final endpoint
https://developers.dwolla.com/llms.txt
HTTP status
200
Content type
text/plain; charset=utf-8
Text retrieval
Firecrawl literal text capture
Tokenizer
tiktoken 0.14.0 · o200k_base
SHA-256 of saved UTF-8 text
b50757650d8611a68986d3f6affdc76003d18913e9d09aa18c4549c5cde1e54e

Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.

Related tools and resources

Contact Jon