Multi-Gateway and i18n Checkout for Food Delivery Marketplaces

Worldwide buyers do not share one checkout culture. A package must support multi-gateway initialize and i18n (copy, currency formatting, RTL) without forking the customer app per country.

Payment initialize as a product surface

• Admin-configurable gateways (keys, webhooks, currencies)
• Wallet / cash / card paths where the market needs them
• Refund and failed-payment behavior documented for ops

i18n that survives production

• String catalogs for customer, driver, restaurant, and admin
• RTL layout for Arabic (and similar) without broken maps or carts
• Currency and tax fields owned by Admin, not hard-coded in clients

What to verify in demos

Switch language, open checkout, and confirm the same order still reaches restaurant and driver clients. See payments & channels and live demos.