Orientation
Org configuration
Six settings Business Development configures on your org at onboarding. They apply to every contract you run — your team never passes them per API call, and the API rejects any attempt to override them per request.
The settings
| Setting | Default | What it means for your contracts |
|---|---|---|
| Invitation | Off | Whether parties must accept an invitation in the Waffy app before they can pay, or are joined automatically when your system adds them. Businesses with repeat, trusted parties usually want auto-join; one-off sales may prefer the invitation gate. |
| Delivery | On | Whether your contracts run through the delivery-confirmation phase at all. For businesses where there's no physical delivery step (digital goods, completed services), this can be turned off so contracts flow straight from payment to settlement. |
| Inspection | Off | Whether contracts include a post-delivery inspection window — a period where the buyer can examine the item after delivery before your team sends the settlement request. Useful for high-value goods. |
| Absher identity verification | Off | Whether your platform requires buyers to verify their Saudi National ID via Absher before paying. You decide whether to require it or make it optional. Waffy provides the verification endpoints — you own the UX. Relevant when KYC of Saudi nationals is a business or regulatory requirement. |
| Allowed payment methods | Per agreement | Any subset of Mada, Visa, Mastercard, Apple Pay, STC Pay, Tabby, Tamara, Neo, and manual bank transfer. Methods are enabled per org; the hosted checkout shows only the ones that are on for you. BNPL methods (Tabby, Tamara, Neo) require separate commercial terms and are not included in standard onboarding. |
| Waffy fees per payment method | Per rate card | Each payment method carries its own rate — card networks, BNPL partners, and bank rails each have different costs. Negotiated once at onboarding, deducted from your settlement proceeds on every transaction. Full details: Payment methods & fees. |
Why these live at org level, not per contract
All six settings affect compliance, commercial terms, or both. They are not something a developer should toggle from a request body. Passing invitationAllowed, isDeliverable, isInspectable, or fee overrides in an API call is rejected. To change any of these after onboarding, contact your Waffy account manager.
Next
- Sandbox & credentials — what arrives in your hands after onboarding is done.