Stripe payments

The restaurant problem

Taking card payments on a restaurant website without becoming a card storage business.

How Codefusion solves it

The restaurant is the Stripe Connect merchant (Express). Customers pay the restaurant. Codefusion does not store card numbers. Application fees exist in the data model and stay at zero until Codefusion approves platform fees.

What is included

Pay up front, webhook-verified payment, refunds from the dashboard within rules, Apple Pay / Google Pay when Stripe and the domain allow them.

How installation and onboarding work

Connect onboarding (Account Link still to be wired). Test-mode account ids can be stored until go-live. A test paid order is required before live traffic.

The commercial benefit

Money lands with the restaurant. Codefusion is not merchant of record for food.

Who it suits

Every restaurant that takes paid orders on the platform.

What Codefusion manages

Connect platform account, webhook endpoint, test procedure.

What the restaurant manages

Bank details in Stripe Express, payouts, their own Stripe disputes.

Hardware requirements

None for taking the payment. The terminal is for accepting the kitchen ticket, not for card-present till payments.

Support provided

Platform payment faults are Codefusion. Stripe account and bank issues are the restaurant plus Stripe.

Frequently asked questions

Who gets the money?

The restaurant. Codefusion does not hold food-order funds.

Is VAT included in the public price?

Public prices are PRICE_PLACEHOLDER until finance approves figures and VAT treatment.