The challenge
An existing Laravel platform needed crypto wallets, balances and withdrawals using two outside providers.
What we built
- Laravel services for the MPC wallet API and the Yativo crypto API
- Linked records for user, customer, asset and wallet
- Balance refresh and withdrawal requests with local transaction records
- API layer ready for the Flutter mobile app
The full story
The situation
A fintech payments platform built on Laravel needed crypto wallets: creating wallets, showing balances and handling withdrawals. It had to use two outside providers, an MPC wallet service and the Yativo crypto API, without changing either.
What we built
A Laravel integration layer with separate service classes for each provider. The MPC service handles wallet execution and signing, Yativo handles customers and assets, and Laravel ties users, wallets and transactions together for the dashboard and a future Flutter app.
The hard part
A Laravel user, a Yativo customer, a customer asset and an MPC wallet each have their own ID. We mapped them explicitly in the database, so the dashboard always asks for the right balance, shows the right address and links a withdrawal to the right wallet.
What testing showed
A test wallet was created on the MPC test server. A test withdrawal reached Yativo and came back asking for two-factor authentication, a provider requirement the withdrawal flow now accounts for. Full live end-to-end runs remained on the validation list.