Display
Price and consent state
Decide the shown currency, rounding, recurring terms, fees, tax display, cancellation information, directionality, and accessible errors. Obtain business and professional approval where required.
Transaction control / ILS
A payment button is the smallest part of the payment system.
The useful scope connects what the customer sees to provider eligibility, settlement, reconciliation, customer support, accounting ownership, and recovery from every meaningful failure.
Provider
Account responsibility
The client confirms provider availability, merchant eligibility, contracts, settlement account, authentication flow, prohibited-use rules, and production credentials.
Failure
Interrupted transactions
Model declines, timeouts, duplicate callbacks, stale sessions, partial fulfillment, provider outages, and an honest customer state when success is unknown.
Aftercare
Refund and dispute route
Name who receives requests, verifies the transaction, initiates a refund, handles chargebacks, records evidence, and communicates the result.
Books
Reconciliation and invoices
Connect order identifiers, provider references, settlement reports, exceptions, invoices, and record retention. Engineering can support the workflow; accounting rules need the proper owner.
Launch
Evidence and monitoring
Use sandbox and controlled production tests, webhook logs, accessible states, alert thresholds, rollback, and a named person who decides whether transactions remain open.
Research can begin with the Bank of Israel payment-systems information and the Israel Tax Authority. Those sources do not replace provider, accountant, tax, or legal review for the actual business.
Transaction packet
Sketch a successful payment and three bad outcomes.
That gives engineering enough truth to design reliable state changes without pretending to choose the commercial or tax route for the client.