Treat the purchase as a complete experience.

A customer selects a product using a Hebrew description and a Latin item code, then reaches a payment step with an unclear currency or status. We build commerce journeys around the merchant's approved arrangement so that the buyer and staff understand the same order.

Establish the actual merchant setup

The selling business selects its provider and confirms account ownership, merchant eligibility, supported currencies, settlement and permitted payment methods. We inspect the relevant account and documentation before promising an integration. No method is assumed to be universally available to businesses or customers in Israel.

The business also supplies approved pricing, tax treatment, returns and customer disclosures with suitable advice. Interface design should preserve those decisions through product selection, checkout and the resulting order; it should not infer a conversion rate or tax position.

Follow a pending purchase

For a hypothetical purchase, retain the selected item code and variant beside the reviewed customer-language description. If the provider result is pending or uncertain, the page should explain the current position without announcing a completed sale. Staff need a recognisable reference and a way to establish the actual result before asking the customer to pay again.

The merchant decides whether stock is held during that interval and how a customer requests cancellation. A cancellation request and a confirmed refund are different outcomes. Test those distinctions against the selected provider rather than an idealised screen design.

Make the shop manageable

Scope can include range organisation, stock ownership, delivery rules and the staff order view. Try a changed variant, rejected payment and corrected contact detail in each required language. A practical initial range may be better than a broad launch with unresolved fulfilment rules.

Bring representative products and the status of the intended merchant account. Assess an online shop →