The team that ships Stripe end to end
We are a Madrid-based software studio with Stripe projects running in production: marketplaces on Connect, SaaS on Billing, migrations away from local gateways and reconciliation against the client's ERP. We work with product teams that need payments to work on day one.
Soamee is a software studio founded in Madrid in 2017 that implements Stripe as its clients' technical partner. Our work covers the full lifecycle of a payments rollout: designing the billing model, building on the Stripe API (Payment Intents, Billing, Connect, Terminal), reliable webhook processing, migrating away from local gateways such as Redsys, automatic reconciliation against ERPs like Holded, A3ERP or SAP, and support after go-live. We have done it for delivery marketplaces, sports booking platforms, B2B SaaS and e-commerce, with teams working in Spanish, English, Portuguese, Italian and German. Companies contract their account directly with Stripe: we bring the engineering team that turns it into a payment flow in production.
An implementation partner, not a checkout integrator
The hard part of a payments integration is never the checkout: it is the in-between states, the disputes, the retries and the accounting.
Whole product, not just payments
We build the entire product — web, mobile app, backend, admin panel — so payments are designed inside the real business flow instead of bolted on at the end.
Edge cases from day one
Idempotent retries, dunning, partial refunds, disputes, mid-cycle plan changes and drift between Stripe and your database. We treat them as requirements, not incidents.
Accounting actually connected
Every charge and payout lands in the client ERP with its invoice and its journal entry. We integrate with Holded, A3ERP, SAP, Odoo and Dynamics 365.
Five languages, European market
Team and documentation in Spanish, English, Portuguese, Italian and German. We know the local payment methods that move conversion in each market.
Compliance as a requirement
SCA and PSD2, PCI DSS through Elements and Checkout, GDPR and data retention. The architecture comes out of design already aligned, not patched after the audit.
Support after go-live
Monitoring of the first real transactions, a payment metrics dashboard and a team that is still around when the first traffic spike arrives.
Which Stripe products we implement
Connect for marketplaces
Seller onboarding with KYC, connected accounts, split payments, holds and scheduled payouts. Includes the dashboard where each seller sees their settlements.
Billing and subscriptions
Plan catalogue, trials, prorations, add-ons, usage-based pricing, dunning for failed charges and a customer portal for sign-ups, cancellations and plan changes without a support ticket.
Checkout and Elements
Embedded or hosted checkout, wallets (Apple Pay, Google Pay), local methods (SEPA, iDEAL, Bancontact, Bizum) and 3D Secure. Optimised for conversion and properly measured.
Terminal and in-person payments
For businesses with a physical location: counter payments unified with the online channel, so the till, the online order and the accounting all speak about the same record.
Migrations from local gateways
An orderly exit from Redsys or other gateways towards Stripe: temporary coexistence of both, migration of active subscriptions and tokenised cards, without interrupting billing.
Reconciliation and reporting
Charges, fees, refunds and payouts synced with the ERP and the accounting close, plus payment metrics dashboards for business and finance.
Got a payments project that needs a team?
Tell us about it →Where we have already walked the path
Sectors where we have product in production and understand the billing model before the first meeting.
Delivery and hospitality
Orders split between restaurant and platform, tips and in-venue payments.
Proptech and self-storage
Recurring rents, deposits, mid-month sign-ups and cancellations.
Sports and leisure
Bookings, prepaid passes, premium subscriptions and in-app payments.
B2B SaaS
Per-seat or usage-based plans, annual billing and enterprise contracts.
E-commerce and marketplaces
Multi-vendor, multi-currency and partial refunds.
Industry and services
Recurring service billing wired into the ERP and the accounting close.
How we work alongside Stripe teams
Four ways into a project, depending on where the client stands.
Full implementation
The client opens their Stripe account and we bring the engineering team: payment model design, development, testing in test mode and go-live.
Integration rescue
We step into an integration already under way that does not add up: dropped webhooks, drifting states or impossible reconciliation. We audit, prioritise and fix.
Migration from another gateway
We run the move from a local gateway to Stripe keeping subscriptions alive, with no cut-off window for the business.
Team extension
We join the client's in-house team for the payments layer, bringing our own testing and observability practices into their repository.
Stripe running in production
What we build with
Our relationship with Stripe
Soamee is an independent software studio. We do not resell Stripe nor act as its agent: every client contracts their account directly with Stripe and keeps ownership of their funds, their data and their commercial relationship.
What we bring is the engineering team that takes that account to production and maintains it afterwards. Stripe and its product names are trademarks of Stripe, Inc., referenced here solely to describe the technical work we do.
Frequently asked questions
Do you work on the client's own Stripe account?
Can you take over an integration that already exists?
Can you migrate from Redsys to Stripe without interrupting billing?
Which countries and languages do you work in?
Shall we talk about your payments project?
Tell us the billing model and the current state of the integration. We will tell you what we would do, in what order and with which team.
Tell us your challenge. We'll propose a solution.
No commitment. Within 24 hours, you'll receive a proposal with scope, timeline and budget. No fine print.