Automate KYC and AML checks on subscription requests with the Regpit integration.
Regpit 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.
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.
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):
A customer submits a subscription request for a plan with an active Regpit connection.
anny automatically creates a case in Regpit and prompts the customer by email to verify.
anny transmits the existing customer and company data to Regpit, where the identity check runs via a video process.
Regpit assesses the overall risk and returns the result to anny via webhook.
If the risk is at most at the defined maximum risk level and all data is present, the subscription request is confirmed.
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.
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.
2
Create the webhook configuration
Create the webhook configuration and share the values with Regpit:
Click Generate webhook configuration.
Copy the created values (Webhook URL, Tenant ID, Webhook token, and User email) via Copy all to clipboard.
Forward the values to your contact at Regpit, so Regpit can set up the webhook on their side.
Click Test webhook connection. anny checks whether a test message arrives from Regpit. Without a successful test, the integration cannot be activated.
3
Choose a verification strategy
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.
4
Connect a subscription plan
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.
5
Activate the integration
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.
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.
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.
Does every subscription request have to go through Regpit?
No. The check only affects subscription plans you have explicitly assigned the Regpit connection to. All other plans remain unaffected.
Where do I see the current status of the check?
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.
What happens if the risk is too high?
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.
What is the difference between verification before and after subscription start?
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.
Are private individuals without a company also checked?
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.
Do admins additionally have to work in Regpit manually?
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.
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.
The verification is complete, but the subscription request stays unconfirmed
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.
Customers keep receiving verification reminders after a successful check
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.