Pay by Bank
Introduction to Straddle’s unified API for account-to-account payments
Pay by Bank is Straddle’s core product, providing a unified API for account-to-account payments. It combines identity verification, open banking connectivity, and payment processing to offer developers a streamlined solution for implementing secure and efficient payment flows.
Technical Components
Pay by Bank consists of three main components:
Identity
Graph-based identity engine for real-time verification
Bridge
Open banking connectivity suite for account linking and paykey generation
Payments
Send or receive payments directly from any bank account
Key Features for Developers
- Unified API: Single integration point for identity, open banking, and payments
- Real-time Identity Verification: Sub-second customer onboarding, no selfies required
- Bank Account Connectivity: Connect to 90%+ of US bank accounts with our Bridge SDK or bring your own token
- Fraud Prevention: Built-in transaction monitoring
- Multi-rail Orchestration: Optimize for speed across ACH, RTP, and FedNow (coming soon)
- Webhook Support: Real-time notifications for asynchronous events
Bridge also supports bank routing and account numbers
This feature is particularly useful for existing customers or in situations where an open-banking connection isn’t possible.
Integration Overview
Implementing Pay by Bank involves interacting with three primary API endpoints:
- Customers API: Manage customers with Straddle ID built-in
- Bridge API: Handle bank account connections and paykey generation
- Payments API: Initiate and manage payment transactions across multiple rails
Implementation Workflow
Customer Onboarding
Use the Customers API to create and verify customer identities.
Open Banking
Implement the Bridge API to securely link customer bank accounts and generate Paykeys.
Payment Processing
Utilize the Payments API with generated paykeys to initiate and manage transactions.
Webhook Handling
Set up webhook endpoints to receive real-time updates on transaction statuses and other events.
For detailed information on request/response formats, parameters, and endpoint-specific functionality, refer to our comprehensive API reference: