slug: dwolla provider: Dwolla generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Banking & Capital Markets min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 7 edges: - tag: transfers spec_file: dwolla-transfers-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.92 evidence: POST /transfers initiateTransfer 'Initiate a transfer'; POST /transfers/{id} cancelTransfer; GET /transfers/{id}/failure 'Retrieve a transfer failure reason'; schemas RtpAccountSettingNotEnabledError, WireAccountNotFoundError reason: 'Core money-movement surface: initiating, cancelling and inspecting ACH/RTP/wire transfers including fees and failure reasons — payment instruction capture, validation and authorisation.' - tag: mass payments spec_file: dwolla-mass-payments-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.9 evidence: POST /mass-payments initiateMassPayment 'Initiate a mass payment'; 'List items for a mass payment'; schema TransferAmount reason: Operations capture and submit batches of payment instructions (mass payment with items) on an ACH/RTP rail, which is payment instruction capture and authorisation. - tag: beneficial owners spec_file: dwolla-beneficial-owners-api-openapi.yml capability_id: BC-1300.20 capability_id_l1: BC-1300 capability_name: KYC & Customer Due Diligence Management confidence: 0.85 evidence: POST /customers/{id}/beneficial-ownership certifyBeneficialOwnershipForCustomer Certify beneficial ownership; GET /customers/{id}/beneficial-ownership getBeneficialOwnershipStatusForCustomer reason: Capturing, verifying and certifying beneficial owners (with passport/address schemas) is the beneficial-ownership component of customer due diligence required of financial institutions, mapping to KYC & Customer Due Diligence Management. - tag: webhook subscriptions spec_file: dwolla-webhook-subscriptions-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.85 evidence: POST /webhook-subscriptions createWebhookSubscription 'Create a webhook subscription'; schema WebhookSubscription, MaxSubscriptionsReachedError reason: Lifecycle management of outbound webhook subscriptions for platform events — developer-platform event subscription management, not a banking business capability. - tag: webhooks spec_file: dwolla-webhooks-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.8 evidence: GET /webhooks/{id}/retries listWebhookRetries; POST /webhooks/{id}/retries retryWebhook; schema WebhookRetries reason: Inspection and retry of outbound webhook deliveries — event delivery reliability on the developer platform. Technical integration surface. - tag: customers spec_file: dwolla-customers-api-openapi.yml capability_id: BC-1300.10 capability_id_l1: BC-1300 capability_name: Customer Onboarding Management confidence: 0.7 evidence: POST /customers createCustomer Create a customer; schemas UpgradeToVerifiedPersonal, CreateVerifiedBusinessCustomerWithController, VerifiedSolePropCustomer, SuspendCustomer reason: Operations create and upgrade payment customers through verified/unverified states with controller and business-classification data — account opening with identity verification for a financial services platform, i.e. Customer Onboarding Management. Some overlap with customer information maintenance keeps confidence moderate. - tag: funding sources spec_file: dwolla-funding-sources-api-openapi.yml capability_id: BC-1340 capability_id_l1: BC-1340 capability_name: Payments & Card Management confidence: 0.7 evidence: POST /funding-sources/{id}/micro-deposits initiateOrVerifyMicroDeposits; GET /funding-sources/{id}/ach-routing getVanRouting Retrieve VAN account and routing numbers; POST /on-demand-authorizations createOnDemandTransferAuthorization reason: Operations establish and verify the bank/card instruments used to move money (micro-deposit verification, ACH routing numbers, balances, transfer authorisations) — payment instrument and authorisation management within Payments & Card Management. Spans instrument setup and payment authorisation, so no single L2.