# Forte.io

## Docs

- [Verification Flows](https://docs.fortepayments.io/access_levels_flows.md): Preview UI flows and identity requirements for access levels 1 through 3 in the Forte Compliance widget.
- [Product Overview](https://docs.fortepayments.io/access_levels_guide.md): Preview Forte Compliance features and access levels.
- [Access Control Level Contract](https://docs.fortepayments.io/acl_contract.md): Overview of the on-chain Access Control Level (ACL) smart contract.
- [Request Access Token](https://docs.fortepayments.io/api-reference/endpoint/authentication.md): Use your `client_id` and `client_secret` to     request an access token to authorize your API requests.
- [Create Payment Intent](https://docs.fortepayments.io/api-reference/endpoint/create-payment-intent.md): Create a payment intent for a specific transaction type.
- [Create Redirect Intent](https://docs.fortepayments.io/api-reference/endpoint/create-redirect-intent.md): Create a payment intent for the customer to be redirected on hosted UI and make a purchase there.
- [Get Payment Statuses](https://docs.fortepayments.io/api-reference/endpoint/get-payment-statuses.md): Request statuses in batch for payments by their intent ids.
- [Create KYC Intent](https://docs.fortepayments.io/api-reference/endpoint/initiate-kyc-request.md): Request a KYC session for a specific action.
- [Create Subscription](https://docs.fortepayments.io/api-reference/endpoint/notifications/create-subscription.md): Creates and returns a new webhook subscription.
- [Delete Subscription](https://docs.fortepayments.io/api-reference/endpoint/notifications/delete-subscription.md): Delete a webhook subscription with specific ID if it is currently disabled. This action is irreversible.
- [Disable Subscription](https://docs.fortepayments.io/api-reference/endpoint/notifications/disable-subscription.md): Disable a webhook subscription with specific ID if it is currently enabled.
- [Enable Subscription](https://docs.fortepayments.io/api-reference/endpoint/notifications/enable-subscription.md): Enable a webhook subscription with specific ID if it is currently disabled.
- [Get Subscriptions](https://docs.fortepayments.io/api-reference/endpoint/notifications/get-subscriptions.md): Get webhook subscription(s) belonging to the merchant.
- [Replay Webhook](https://docs.fortepayments.io/api-reference/endpoint/notifications/replay-webhook.md): Replay webhook with the given id,     given linked subscription is still enabled.
- [Replay Webhooks](https://docs.fortepayments.io/api-reference/endpoint/notifications/replay-webhooks.md): Replay all webhooks sent out in time range,       given linked subscription is still enabled.
- [Test Subscription](https://docs.fortepayments.io/api-reference/endpoint/notifications/test-subscription.md): Post a test webhook to the webhook subscription with specific ID.
- [Update Subscription](https://docs.fortepayments.io/api-reference/endpoint/notifications/update-subscription.md): Update a webhook subscription with specific ID.
- [Get Widget Manifest](https://docs.fortepayments.io/api-reference/endpoint/widget-manifest.md): Response payload includes widget version and integrity digest (SHA-384)
- [Compliance Events](https://docs.fortepayments.io/compliance/compliance-events.md): Client-side events emitted by the Forte Compliance widget. Use these to update your UI after verification completes or the widget is closed.
- [Create KYC Intent](https://docs.fortepayments.io/compliance/initiate-kyc-request.md): Initiate an identity verification request using the Forte Compliance widget.
- [🚀 Get Started](https://docs.fortepayments.io/index.md): Integrate Forte Payments and Forte Compliance into your application.
- [Integrate Widget](https://docs.fortepayments.io/integrate-widget.md): Embed and initialize the Forte widget in your frontend. This step is the same for both Forte Payments and Forte Compliance.
- [Introduction](https://docs.fortepayments.io/introduction.md)
- [Obtain Access Token](https://docs.fortepayments.io/obtain-access-token.md): Authenticate with Forte using OAuth2 client credentials. Required before creating a payment intent or initiating a KYC request.
- [Create Payment Intent](https://docs.fortepayments.io/payments/initiate-payment-request.md): Initiate a VDG (Virtual Digital Goods) payment session using the Forte Payments widget or redirect mode.
- [Introduction](https://docs.fortepayments.io/payments/introduction.md): Forte Payments enables gaming and digital asset platforms to accept fiat and crypto payments for Virtual Digital Goods - with built-in compliance, no sensitive data on your servers.
- [Payment Events](https://docs.fortepayments.io/payments/payment-events.md): Client-side events emitted by the Forte Payments widget. Use these to update your UI after a payment completes or the widget is closed.
- [Testing](https://docs.fortepayments.io/payments/testing.md): Test cards, sandbox OTP codes, and environment details for Forte Payments.
- [Pay with Card](https://docs.fortepayments.io/payments/vdg-pay-with-card.md): End-to-end widget flow for a Virtual Digital Good purchase using a credit or debit card.
- [Webhooks](https://docs.fortepayments.io/payments/webhooks.md): Subscribe to server-side payment status events from Forte. Webhooks are the authoritative signal for delivering Virtual Digital Goods.

## OpenAPI Specs

- [openapi-notifications](https://docs.fortepayments.io/api-reference/openapi-notifications.json)
- [openapi-payments](https://docs.fortepayments.io/api-reference/openapi-payments.json)
- [openapi-auth](https://docs.fortepayments.io/api-reference/openapi-auth.json)