Services and features
The capabilities a business turns on: what's supported, how to enable and configure a service and its features, and how a service moves through its own status lifecycle.
A business you onboard can't use Priority until you turn on what it needs. A service is something the business can do through Priority, such as Accept Payments, which lets it take card payments. A feature is an option you switch on or off within a service. Onboarding provisions Accept Payments (card-not-present), the service services.payin.card, with its features.
Priority approves each service on its own. Before a service can be used, Priority checks that it can approve the business for it; this check is underwriting. So each service has its own status and its own list of what it still needs before it can go live.
| Term | What it is | Example |
|---|---|---|
| Service | Something the business can do through Priority. You turn it on, and Priority approves it. | Accept Payments (payin.card) |
| Feature | An option within one service that you switch on or off. | 3-D Secure, an extra check on online card payments |
You set services and features for the whole business, or differently at one location.
In this section
The service and feature codes a business can turn on, and what each one does.
Enable or disable a service and switch its features on or off, for the whole business or one location.
The statuses a service moves through as it is enabled, reviewed, and disabled.
See also
- Businesses: where services sit in the entity model
- Status lifecycle: the business-level boarding flow a service feeds into
Updated 9 days ago