Before processing payments, you’ll need to have verified customers and connected bank accounts set up through Straddle’s Identity and Bridge services.
Core Payment Concepts
Straddle organizes payment operations into three primary concepts:Charges
Collect money from your customers’ bank accounts
Payouts
Send money to your customers’ bank accounts
Funding Events
Track money movement between Straddle and your business
Understanding the Flow
When you process payments through Straddle:- Charges pull money from customer accounts into Straddle’s network
- Payouts push money from Straddle’s network to customer accounts
- Funding Events represent the settlement of these transactions to your business bank account
Payment Rails
Straddle automatically optimizes payment routing across multiple rails to balance speed, cost, and reliability. You don’t need to specify which rail to use - Straddle selects the optimal option automatically:ACH (Automated Clearing House)
ACH (Automated Clearing House)
Processing Time: 1-3 business daysUse Cases:
- Standard recurring payments
- High-value transactions
- Batch processing
- Lower cost per transaction
- Higher daily limits
- Reversible for up to 60 days
RTP (Real-Time Payments)
RTP (Real-Time Payments)
Processing Time: SecondsUse Cases:
- Instant disbursements
- Time-sensitive payments
- Enhanced customer experience
- 24/7/365 availability
- Irrevocable once completed
- Maximum $1 million per transaction
FedNow
FedNow
Processing Time: SecondsUse Cases:
- Government payments
- Instant settlement needs
- Critical payment flows
- Federal Reserve operated
- 24/7/365 availability
- Enhanced security and compliance
Same Day ACH
Same Day ACH
Processing Time: Same business dayUse Cases:
- Urgent business payments
- Payroll disbursements
- Time-sensitive refunds
- Multiple processing windows daily
- Business days only
- Higher limits than standard ACH
Quick Start Example
Here’s a complete payment flow from customer creation to fund settlement:1
Create a verified customer
First, onboard your customer through Straddle’s Identity service:
2
Connect a bank account
Use Bridge to securely link the customer’s bank account and generate a paykey:This returns a session for the customer to complete bank authentication, resulting in a
paykey
.3
Create a charge
Use the paykey to charge the customer:
All fields shown are required. See the charges guide for complete parameter documentation.
4
Monitor the payment
Track the charge status through webhooks:
created
→ Payment initiatedscheduled
→ Queued for processingpending
→ Sent to payment networkpaid
→ Successfully completed
5
Reconcile funding
View the corresponding funding event once the payment settles:Learn more about funding and reconciliation.
Payment Security
Straddle implements multiple layers of security for payment processing:Transaction Monitoring
Real-time fraud detection and risk scoring on every transaction
Balance Verification
Optional pre-transaction balance checks to reduce NSF returns
Velocity Controls
Configurable limits on transaction amounts and frequency
Hold & Review
Ability to pause suspicious transactions for manual review
Common Workflows
Recurring Subscriptions
Process regular charges using stored paykeys:- Store customer paykeys after initial authentication
- Create charges on your billing schedule
- Handle failures and retries automatically
- Update payment methods when needed
Marketplace Payouts
Distribute funds to your sellers or service providers:- Verify recipient identity and bank accounts
- Create payouts with detailed descriptions
- Track payout status and handle failures
- Reconcile platform fees and net settlements
Instant Transfers
Provide immediate fund availability:- Use RTP rail for sub-second processing
- Verify account eligibility for instant payments
- Handle fallback to standard ACH if needed
- Communicate clear timing to customers
Testing Payments
Straddle provides comprehensive sandbox testing capabilities:- Deterministic outcomes - Control payment success/failure scenarios
- Accelerated processing - Payments process in minutes instead of days
- Webhook simulation - Test your event handling logic
- Error scenarios - Simulate NSF, closed accounts, and returns