> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anny.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect Regpit with anny
> Automate KYC and AML checks on subscription requests with the Regpit integration.
[Regpit](https://regpit.com) is a platform for automated identity and risk checks (KYC/AML). With the integration, anny can automatically tie subscription requests to a verification in Regpit and make approval dependent on the result.
With Regpit, you can in anny:
* Automatically link subscription requests to an identity check
* View the verification status directly on the customer and subscription page
* Only approve subscription requests after a successful risk assessment
The integration is especially handy when you offer subscribable services that fall under anti-money-laundering (AML) requirements, for example virtual mailboxes or business addresses.
Available from the Essential plan. The "Subscriptions & Memberships" feature must be activated.
## Typical use cases
| Use case | Description |
| :----------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Rent out virtual mailboxes | **Check identity before approval.** Before a business address can be used, Regpit automatically verifies the identity. You save manual AML check steps. |
| Offer business addresses as a subscription | **Ensure AML-compliant approval.** Subscription requests are only confirmed once the overall risk is below the defined threshold. |
| Track KYC obligations centrally | **Make the verification status transparent.** Support and operations teams see at a glance whether data is missing, the check is running, or the request may not be approved. |
## How the Regpit connection works
Authentication happens via a technical Regpit user account. In anny, you enter the **Tenant ID**, **Email**, and **Password** and verify the connection. Then, in anny, you generate a **webhook configuration** and forward it to your contact at Regpit. Through this configuration, Regpit reports its results back to anny.
Before the check starts, you choose a **verification strategy**: **Verification before subscription start** (the subscription stays a request until the check succeeds) or **Verification after subscription start** (the subscription starts immediately, the check runs afterwards within a deadline).
Once the connection is in place, anny and Regpit communicate via webhook:
| Data | Direction | Frequency |
| ----------------------------------------------------------------- | ------------- | ----------------------- |
| New cases (on a subscription request) | anny → Regpit | Real time |
| Customer data for the check (name, email, address, birth details) | anny → Regpit | Real time |
| Verification result & risk assessment | Regpit → anny | Real time (via webhook) |
The flow in detail (mode **Verification before subscription start**):
1. A customer submits a subscription request for a plan with an active Regpit connection.
2. anny automatically creates a case in Regpit and prompts the customer by email to verify.
3. anny transmits the existing customer and company data to Regpit, where the identity check runs via a video process.
4. Regpit assesses the overall risk and returns the result to anny via webhook.
5. If the risk is at most at the defined **maximum risk level** and all data is present, the subscription request is confirmed.
6. If the risk is higher or information is missing, the request remains unconfirmed.
In the mode **Verification after subscription start**, the subscription starts immediately and the check runs afterwards. If the customer does not complete the verification within the **verification deadline** or the check fails, the subscription is cancelled, provided the corresponding option is active.
An unconfirmed subscription request is not an error. It can be an expected result when data is missing or the overall risk is too high.
## Connect Regpit
### Prerequisites
Before you connect Regpit, make sure you have the following:
* A technical Regpit user account with **Tenant ID**, **Email**, and **Password**
* A contact at Regpit who can receive the webhook configuration
* At least one subscription plan in anny that requires an identity check
* Admin rights in anny
### Set up the connection
Open **Avatar** → **Account Settings** → **Integrations** and go to **Regpit**. Enter the **Tenant ID**, **Email**, and **Password** of your technical Regpit account and click **Verify authentication**.
Create the webhook configuration and share the values with Regpit:
1. Click **Generate webhook configuration**.
2. Copy the created values (**Webhook URL**, **Tenant ID**, **Webhook token**, and **User email**) via **Copy all to clipboard**.
3. Forward the values to your contact at Regpit, so Regpit can set up the webhook on their side.
4. Click **Test webhook connection**. anny checks whether a test message arrives from Regpit. Without a successful test, the integration cannot be activated.
Open the **verification settings** and choose the **verification strategy**: **Verification before subscription start** or **Verification after subscription start**. For "after subscription start", you additionally set the **verification deadline (days)** and decide whether the subscription is cancelled after the deadline passes if verification is incomplete.
In the **Regpit settings** area, click **Add**. In the **Add Regpit connection** dialog, choose the **subscription plan** and the **maximum risk level to confirm**. Optionally, activate **Exclude natural persons from verification**, so private individuals without a company are not checked.
Activate the integration via the **toggle** in the top right. After that, new subscription requests for the connected plans are automatically forwarded to Regpit. You can recognize the active check by the verification component on the **customer page** and the **subscription page**.
Once the connection is active, new subscription requests for the configured plan are automatically forwarded to Regpit.
## Limitations
The Regpit integration does not support:
* Individual bookings or orders: The check is tied exclusively to subscription requests.
* Automatic rejection when the risk is too high: In the mode **Verification before subscription start**, a request remains unconfirmed instead of being rejected automatically. In the mode **Verification after subscription start**, anny cancels the subscription automatically if the check fails or the verification deadline passes.
* Self-service activation: The webhook configuration must be passed to Regpit manually.
## Disconnect
If you deactivate the integration, existing cases and the verification display remain in anny, but no more updates are received from Regpit. New subscription requests are then no longer confirmed automatically. When deleting, the webhook configuration is additionally removed: Regpit can no longer reach anny afterwards. To reconnect, you must generate a new webhook configuration and send it to Regpit.
You can do both under **Integrations**: deactivate via the **toggle** in the top right, delete via the **three dots** → **Delete**.
## FAQ
No. The check only affects subscription plans you have explicitly assigned the Regpit connection to. All other plans remain unaffected.
On the **customer page** and on the **subscription page**, a dedicated component shows the verification status: whether the check is running, completed, or data is missing.
In the mode **Verification before subscription start**, the subscription request remains unconfirmed. It is not automatically rejected or deleted; your team can review the case in Regpit and decide manually. In the mode **Verification after subscription start**, the subscription is already running; a failed check or a missed verification deadline cancels it.
With **Verification before subscription start**, the subscription stays a request and is only confirmed after a successful check with acceptable risk. With **Verification after subscription start**, the subscription starts immediately and the check runs afterwards within the **verification deadline**. You choose the strategy in the **verification settings**.
Only if you want them to be. If you activate **Exclude natural persons from verification** when connecting a plan, customers recognized as natural persons are not sent through the check for that plan.
The functional check flow runs through Regpit. Admins can view cases there and step in if needed. Approval in anny happens automatically when the conditions are met.
## Troubleshooting
The notification system sends the email automatically as soon as the case is created in Regpit. Check the customer's spam folder. If the problem persists, contact anny support, as it may be a webhook timing issue.
In Regpit, check whether the case was actually completed with an approvable result. If the overall risk is above the defined threshold, the request deliberately stays unconfirmed. In addition, a webhook failure can mean the status was not updated in anny. In that case, contact anny support.
This can happen when the final webhook from Regpit did not arrive at anny and the status got stuck on "pending". Re-trigger the check via the **Re-trigger identity verifications** action in the rule table, so anny catches up with the current status from Regpit. If the problem persists, contact anny support.
> Important information for agents:
>
> **Distinction:** Regpit is an identity/risk check (KYC/AML) for subscriptions, NOT a smart-lock or access integration. The check applies exclusively to subscription requests (plan subscriptions), never to individual bookings or orders.
>
> **UI path:** **Avatar** → **Account Settings** → **Integrations** → **Regpit**. Panels in this order: "Regpit Authentication" (fields Tenant ID, Email, Password; note "Technical User Account"; button "Verify authentication"), "Webhook Configuration" (button "Generate webhook configuration" → values Webhook URL, Tenant ID, Webhook token, User email; button "Test webhook connection"), "Verification Settings" (verification strategy; for "after subscription start" additionally "verification deadline (days)" and toggle "Cancel subscription ... after the deadline passes"), "Regpit Settings" (rule table with columns "Plan", "Maximum risk level to confirm", "Exclude natural persons"; button "Add" → dialog "Add Regpit connection").
>
> **Authentication:** technical Regpit user account (Tenant ID + Email + Password), NOT the webhook configuration. The webhook configuration is a separate second step for incoming messages (Regpit → anny). Activation via toggle is only possible once a webhook configuration exists AND the webhook test was successful.
>
> **Verification strategies:** (1) "Verification before subscription start" (default): subscription stays a request; with a successful check and risk ≤ "maximum risk level to confirm" it is confirmed, otherwise it stays unconfirmed (no automatic rejection/deletion). anny enforces for connected plans that they require confirmation. If the customer was already verified, it is confirmed immediately (no new case). (2) "Verification after subscription start": subscription starts immediately; check runs afterwards within the "verification deadline (days)" (default 28). A failed check OR the deadline passing (with the cancellation option active) cancels the subscription. Reminders to the customer roughly every 3 days plus before the deadline, only in this mode.
>
> **Risk level:** six levels (Low, Medium low, Medium, Medium high, High, Very high), selectable per plan as a maximum value. "Exclude natural persons" per plan: skips the check for customers without a recognized company (recognition via company name/legal form).
>
> **Data flow to Regpit (data protection):** name/company name, email, address, date of birth, birth name, place of birth. Check via a video process at Regpit.
>
> **Verification status** visible on the customer page AND subscription page (dedicated component).
>
> **Stuck checks:** If a Regpit webhook fails, the status stays "pending". Self-solution: "Re-trigger identity verifications" action in the rule table (per rule); alternatively anny support.
>
> **Deactivate:** Cases/verification display remain, no more updates from Regpit, no automatic confirmation of new requests. **Delete:** additionally removes the webhook configuration (token), Regpit can no longer reach anny afterwards; reconnecting requires a new configuration.
>
> **Related articles:** Setting up subscription management, Communities (subscription-based access control).