Integration Models

Modified on Fri, 13 Mar at 11:06 AM

Depending on your approved use case, you can choose the integration model that best fits your platform. Each model connects to specific API endpoints to ensure smooth operation. If you’re unsure which to use, contact our team for guidance.

1. First Party Transfer (Customer Profile)

For partners collecting payments from and making payouts to their own users only
Users must deposit from and withdraw to a bank account in their name
User information is required for regulatory compliance

2. Third Party Transfer (Customer Profile)

For partners collecting payments and making payouts on behalf of their users
User information is required before transactions can be processed

3. Regular Transfer

For partners managing their own collections and payouts
No first-party or third-party restrictions
Ideal for standard transactions and general payment flows

Integration Model Comparison

	First - Party Transfer	Third - Party Transfer	Regular Transfer
Who is this for?	Businesses that collect payments from users and make payouts to their users' external bank accounts (e.g., crypto exchanges, fintech platforms).	Businesses that collect payments and make payouts on behalf of their users (e.g., payment service providers (PSPs), marketplaces).	Businesses that use StraitsX API to collect payments and make payouts for themselves without handling transactions for other users (e.g., corporate treasury, investment firms).
What does it do?	Users deposit only from their own bank accounts and withdraw only to their own bank accounts—no third-party transactions allowed.	Allows partners to process payments and transfers for multiple users—users transact through the partner’s platform instead of directly with their own accounts.	Enables businesses to move their own funds between accounts for internal financial operations—does not involve third-party users.
Where can funds come from?	User’s personal bank account only.	Enables businesses to move their own funds between accounts for internal financial operations—does not involve third-party users.	Any of the Partner’s corporate bank accounts.
Where can funds be sent?	Only to the user’s personal bank account. (Strictly no other users or third parties)	The partner can send funds to users, merchants, or third parties as directed by the partner.	The partner can send funds to users, merchants or linked corporate bank accounts.
When is this used?	When a business needs a compliant, regulated way to facilitate fiat deposits and withdrawals for its users.	When a business facilitates payments and settlements on behalf of its customers (e.g., a PSP processing online payments for merchants).	When a business needs to move funds between its own accounts for financial operations (e.g., treasury functions).
Why choose this model?	✅ Regulatory compliance – Transactions are restricted to verified users. ✅ Security & KYC – Requires user identity verification.	✅ Scalable payment processing – Ideal for platforms handling multiple transactions. ✅ Merchant-friendly – Enables marketplace-style fund flows.	✅ Secure and controlled fund management – Used for treasury operations. ✅ Streamlined fund movements – Reduces complexity of managing business accounts.
How does it work?	1️⃣ User completes KYC verification. 2️⃣ User deposits from their own bank account. 3️⃣ User withdraws to their own bank account. 4️⃣ StraitsX enforces compliance and transaction tracking.	1️⃣ Partner collects KYC details from users. 2️⃣ Users pay via the partner’s platform. 3️⃣ Partner initiates transactions using StraitsX API. 4️⃣ Funds are transferred to users, merchants, or third parties.	1️⃣ The partner uses its own funds. 2️⃣ Transfers are initiated internally between linked accounts. 3️⃣ Transactions are recorded for business financial tracking.