You can view this page on our documentation site here.
Straddle simplifies the process of building next-generation payments infrastructure directly into your application. This page provides an overview of Straddle’s core concepts, which are essential for understanding and effectively utilizing the API.
Understanding these core concepts is crucial for effectively integrating Straddle into your application. Take your time to familiarize yourself with each component.
Organizations
Manage multiple Straddle accounts from a centralized entity
Accounts
Represent businesses using the core Straddle services
Platforms
SaaS or marketplaces extending Straddle services to users
Customers
End-users involved in payment transactions with an Account
Bridge
Connectivity suite for securely connecting to a Customer’s payment method
Paykeys
Secure tokens linking verified Customers to payment methods
Payments
Transactions between Customers and Accounts
Funding Events
Movement of money between Straddle and Accounts
Detailed Explanations
Organizations
Organizations allow you to manage all your Straddle accounts in one place, streamlining team and role management, customer and payment information searches, and unified reporting across your entire business.
Key features of Organizations:
Manage multiple Straddle accounts from a single, centralized dashboard
Streamline account onboarding by copying KYC information from existing accounts
Get a big-picture view of your business with consolidated metrics and reporting
Centralize team management with inherited roles across accounts
Search for business information across all accounts
Benefits of using Organizations:
Eliminate the need for multiple account logins
Reduce operational overhead
Simplify financial reporting across your entire business
Respond to customer support inquiries faster
Make more informed decisions with cross-account insights
For more details on working with Organizations, see the Organizations API Reference
Note: For businesses working directly with Straddle, an organization and your first account are automatically created when you register for sandbox access. This streamlines your onboarding process and allows you to start exploring Straddle’s features immediately after registration.
Accounts
An account represents a business that has entered into a contractual relationship with Straddle to utilize Straddle’s services directly.
Key points about accounts:
Each account indicates a legal, contractual relationship between a business entity and Straddle.
Accounts can immediately access the Straddle API Sandbox upon creation.
To activate production access, businesses need to provide necessary information via the Dashboard and complete an automatic onboarding process.
For more details on working with Accounts, see the Accounts API Reference
Platforms
A platform is typically a vertical-specific SaaS, two-sided marketplace, or PSP/PayFac that utilizes Straddle Embed to extend Straddle services to its users.
Important aspects of platforms:
Platforms can create and manage Straddle accounts for other businesses.
They can interact with the API on behalf of their users.
If a platform needs to use Straddle services for its own transactions, it should register a separate account.
Platforms use the same account creation endpoint as regu
lar accounts, but with additional configuration:
For more details on interacting with Straddle as a Platforms, see the Platforms Guide
Customers
A customer represents an individual or business involved in a payment transaction with a Straddle account.
Key features of customers:
Customers can be created through the Straddle API.
Upon creation, customers undergo an automatic verification process called Straddle Identity.
The verification process helps prevent fraudulent activities and ensures a secure environment for transactions.
For more details on working with Customers, see the Customers API Reference
Bridge
Bridge is a comprehensive suite of account connectivity endpoints that simplifies the process of securely connecting users’ financial accounts to your application.
Bridge offers:
A drop-in open banking widget that connects to 90% of US bank accounts with a simple code snippet.
Support for existing third-party tokens from providers like Plaid, MX, Flinks, and Finicity (Mastercard).
API-based bank account verification for “out of network” banks, eliminating the need for micro-deposits.
For more details on using Bridge, see the Bridge API Reference
Paykeys
Paykeys represent an evolution of traditional payment tokenization. They create a secure link between a user’s verified identity and their chosen payment method, providing an identity-linked payment solution.
Key benefits of Paykeys include:
Secure linking of verified user identities to payment methods eliminates fraud.
Your application never has to interact with sensitive banking data or store confidential account numbers.
Reusability for subscriptions and recurring payments.
Built-in balance confirmation on every payment.
For more details on working with Paykeys, see the Paykeys API Reference
Payments
A payment represents a transaction between a Customer and an Account. There are two types of payments:
Charges: Used to debit money from a customer for the sale of goods or services.
Payouts: Used to send money to a customer for things like refunds, loan disbursement, or washouts.
Payments are created using Paykeys, which securely link the customer’s identity to their payment method.
For more details on working with Payments, see the Payments API Reference
Funding Events
A funding event represents the movement of money between Straddle and an Account. Funding events are automatically generated as part of a payment and cannot be created directly via the API.
There are two types of funding events:
Deposits: Represent money sent from Straddle to an external bank account linked to an Account.
Deposits are the result of successful charges and represent a settlement for the sale of goods or services.
Withdrawals: Represent money pulled from an external bank account by Straddle.
Withdrawals occur when a Payout is created and represent the money being sent to the Customer.
For more details on working with Funding Events, see the Funding Events API Reference
Note: These core concepts form the foundation of the Straddle API. By understanding and leveraging these concepts, you can effectively integrate the Straddle stack into your applications and create seamless payment experiences for your users.
For more detailed information on each concept and how to implement them using the Straddle API, please refer to the respective sections in our documentation.