01Scope & contract
02Milestone payments
03Reviewable delivery
04Defined support
Agree the details before work begins
A practical framework for delivery in Oman
01
Local payments begin with the merchant account
Oman’s government portal lists an account with a licensed local bank and an integration document for OmanNet gateway access. Merchant onboarding therefore needs to progress alongside payment design; technical integration does not replace the bank’s approval.
Business bank account
Merchant onboarding
Integration specification and testing
02
Test before accepting live payments
Bank Muscat requires a registered business, a business account and an active website or app for gateway applications. Its process includes integration testing before activation. Confirm fees and the delivery schedule directly in the bank’s current offer.
Prepare the documents
Test payment and return flows
Activate after provider approval
03
A quotation with clearly separated costs
Oman’s standard VAT rate is 5%; the treatment of a particular contract depends on the parties and the supply. Our project proposal separates development, hosting, third-party services and tax. The payment route and settlement arrangements are reviewed before the agreement is finalized.
Scope and price per milestone
Third-party service costs
Tax and settlement arrangements
04
Decide how data will be handled early
Oman’s technology ministry describes consent and safeguards for transfers of personal data abroad, with additional requirements for sensitive data. Data categories, processing locations and each party’s responsibilities should be assessed before selecting hosting.
Map the data flow
Access and retention rules
Review cross-border transfers
05
Our proposed approach: reviewable milestones
Work begins with a defined problem and acceptance criteria. Design, development and testing then proceed in agreed delivery packages. Each milestone identifies its approver, acceptance conditions and payment date. Percentages and schedules follow the project’s needs rather than a fixed template.
Discovery and scope
Design and phased development
Acceptance, handover and support planning
06
One product, two complete language experiences
We propose distinct Arabic and English experiences built around shared data and identity. Forms, notifications, documents and payment journeys are tested in both languages. Documentation, knowledge transfer and support responsibilities form part of the handover plan.
Arabic RTL and English LTR
End-to-end business acceptance
Documentation and knowledge transfer
Official sources for further checks
The specific contract, tax treatment and payment route depend on the parties and the service.