Skip to content
Verified

Finance providers

Two payment rails behind Xuda commerce, your own Stripe account or Xuda's own Cardcom terminal.

A store's checkout settles through one of two payment rails, chosen per store with the payments.rail setting: stripe, cardcom, or auto (the store's currency decides). The two rails answer to the same contract, an amount, a currency, an idempotency key and one shared status machine, but they differ in who your buyer's money actually belongs to on its way to you.

Stripe: an account of your own

Connecting Stripe mints you a Stripe Express account: your own dashboard on Stripe's side, your own payout schedule, a real Stripe identity. You do this from Account > Finance in the dashboard, where the embedded onboarding form is styled to match Xuda rather than Stripe's own theme. See Finance for that screen.

Every charge is a direct charge: your buyer's card is charged straight to your Stripe account, Stripe deducts its own processing fee from your balance, and Xuda's application fee is transferred to Xuda in full and never reduces what Stripe itself takes. You are the one who sees a chargeback or a dispute land, because on the Express shape Stripe holds the platform, not the seller, responsible for negative balances, so Xuda carries that exposure rather than passing it to you.

Objects this rail exposes

A connected Stripe account can hold customers, products, prices, quotes, invoices, subscriptions, payment links, refunds, credit notes and coupons. There is no order object on this rail; your store's own orders (commerce_list_orders, commerce_get_order) are Xuda's, not Stripe's, and stay that way regardless of which rail took the payment.

Cardcom: no account to connect

Cardcom needs nothing from you. Every Cardcom charge posts to Xuda's own platform terminal, so Xuda is the merchant of record on this rail and there is no seller onboarding step, no dashboard to sign into, nothing to verify. It exists specifically because Stripe has no path at all to onboard a seller domiciled in Israel, in any account shape; Cardcom does. In exchange for being platform-owned, it also does two things Stripe's rail does not on this store: it offers card installments (capped by your store's own settings) and it issues the Israeli tax document at charge time, which Xuda records a reference to rather than issuing itself.

Availability depends on this server

Both rails answer a capabilities check before either is offered at checkout. A server with no Cardcom configuration, or one where it has been switched off, reports the rail unavailable rather than showing a payment option that would fail.

Choosing between them

auto picks Cardcom for a store whose currency needs it and Stripe otherwise, which is the only default that does not strand an Israeli store with no working rail at all.

Next