Your card processor, your ledger, your messaging and your mailing list stay yours. Trimsy connects to the accounts you already have rather than asking you to move to ours, and takes no commission on anything that passes through them.
Email marketingMailchimp, Brevo, Zoho CampaignsSync customers and leads to Mailchimp, Brevo or Zoho Campaigns and send campaigns from your own provider.Set up in Settings ▸ Integrations.
The principle
You keep the account, and the relationship
Every integration here is bring your own. That is a deliberate choice about who you depend on.
Your payment processor, in your business name, paying out to your bank on your schedule.
Trimsy adds 0% commission on payments. You pay your processor their rate and nothing to us per transaction.
Card numbers are held by the processor, never by Trimsy. We keep a token that can be charged but not read.
Your ledger connection is authorised by you and can be revoked from either end.
SMS reminders work on plan credits whether or not you bring your own Twilio, so nothing breaks if you skip it.
Disconnect any of them and your Trimsy records are unaffected.
There is no such thing. Trimsy is not a payment processor and never holds your money. You connect your own Stripe or Square account and the funds go from them to your bank.
No. Trimsy is a flat monthly subscription with 0% commission. Your card processor charges their standard rate and bills you directly.
An account with whichever service you are connecting, in your business name. For Stripe, Square, Xero, Mailchimp and Zoho you authorise the connection in their own login. Brevo and Twilio use a key or credentials you paste in.
Yes. Payments, accounting, messaging and email marketing are independent of each other, and most businesses run a payment processor long before they connect a ledger.
Future syncing or sending stops and your Trimsy records stay as they are. Anything already sent to Xero stays in Xero. Saved cards are the one thing that does not survive a change of payment processor, because the token only means something to the processor that issued it.
Tell us which one and what you would use it for. That is how the ones on this page got prioritised, and a specific workflow is far more useful to us than a product name.