Webhooks Integration Overview {#wh-fg-workflow-options}
=======================================================

Follow these steps to set up your system to support the Webhooks REST API. Some of these steps are dependent on your system's security policy.

#### Figure:

Set Up Webhook Subscriptions Workflow ![](/content/dam/documentation/cybs/en-us/topics/payments-processing/payment-services/webhooks/images/webhooks-setup-workflow-600x560.svg/jcr:content/renditions/original)
1. Set up a server with a URL to receive webhook notifications.
2. Configure your server security to receive webhooks notifications. For more information, see [Set Up Your Security](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/wh-fg-server-security.md "").
3. Create a REST API security key that is compliant with your security policy. Security keys are used to authenticate the requests you send to `Visa Acceptance Solutions`. You must create separate keys for the testing and production environments. For more information, see [Create REST API Keys](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/webhooks-keys-intro.md "").
4. Request a digital signature key from `Visa Acceptance Solutions`. For more information, see [Create a Digital Signature Key](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/wh-fg-key-dig-sig-intro.md "").
5. If your webhooks integration will include subscriptions to payment event notifications, implement message-level encryption for those events. See [Message-Level Encryption](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/wh-fg-mle-intro.md "").
6. If your system uses the *OAuth* or *OAuth with JWT* security policy, you must provide your OAuth credentials to `Visa Acceptance Solutions`. OAuth is not required and Mutual Trust is the default. If you are not using OAuth, skip this step. For more information, see [(Optional) Provide Your OAuth Credentials](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/wh-fg-oauth-cred-intro.md "").
7. Request a list of the products for which your organization is enabled to receive webhook notifications. For more information, see [Retrieve a List of Products and Events](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/wh-fg-product-list-intro.md "").

   > IMPORTANT
   > If your webhooks integration will include subscriptions to payment event notifications, implement message-level encryption for those events. See [Message-Level Encryption](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/wh-fg-mle-intro.md "").

8. Create your webhook subscription event notifications. For more information, see [Create a Webhook Subscription](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/wh-fg-subscribe-intro.md "").

Optional Set Up Tasks {#wh-fg-workflow-options_opt-tasks}
---------------------------------------------------------

You can complete these optional tasks after creating a webhook subscription.
* Include a health check URL to enable `Visa Acceptance Solutions` to monitor your server's status for reliability. For more information, see [Webhook Health Check URL and Automatic Revalidation](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/wh-fg-optional-intro/wh-fg-subscription-health-check-url.md "").
* Customize the retry policy for unresponsive webhook and health check URLs. For more information, see [Configure the Retry Policy](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/wh-fg-optional-intro/wh-fg-optional-retry.md "").
* Validate your digital signature. For more information, see [Validating a Notification with the Digital Signature Key](/docs/vas/en-us/webhooks/implementation/all/rest/webhooks/wh-fg-key-dig-sig-intro/wh-fg-optional-validate-intro.md "").