With the Regpit Integration, you connect subscription requests in anny to an automated identity and risk check. As soon as a relevant request comes in, anny starts the verification process in Regpit and only confirms the request once all required data is available and the risk is below the defined threshold.
This feature is especially helpful for providers who offer subscription plans that require a KYC- or AML-compliant check before approval. This way, you reduce manual review steps and make the current status more transparent for your team.
Who is this feature for?
This feature is aimed at admins who offer subscription plans in anny and need to verify customers before confirming a request.
Typical use cases:
If you rent out company mailboxes and need to verify identities before approval.
If you offer business addresses or similar subscribable services that fall under AML regulations.
If you don't want to track KYC and AML checks manually outside of anny.
What changes with this feature?
From your customers' perspective:
After a relevant subscription request, customers receive a notice in anny that an identity verification is required.
Customers are redirected to Regpit for verification.
The request is not confirmed immediately but remains pending depending on the result of the check.
From the admin perspective:
For a relevant subscription request, anny automatically creates a case in Regpit.
On the customer page and on the subscription page, there is a new component that makes the status of the identity verification visible.
The confirmation of a subscription request no longer depends solely on the request itself, but additionally on the verification and risk result from Regpit.
Support and operations teams can more quickly assess whether data is still missing, the verification is in progress, or the request must not be confirmed.
Important: An unconfirmed subscription request is not automatically an error in this flow. It can be an expected outcome if data is missing or the overall risk is too high.
Where can you find the feature in anny?
In the account settings under the Integrations tab, you'll find the Regpit Integration, which can be authenticated here.
Requirements and dependencies:
You use Regpit as a connected integration for identity and risk checks.
You offer subscription plans that require verification before confirmation.
A risk threshold is defined for the respective flow, determining when a request is confirmed or not confirmed.
The Regpit integration is authenticated in the anny admin area.
How the logic works
The core logic of the Regpit Integration follows a clear sequence:
A customer submits a subscription request in anny for a plan that requires identity verification.
anny automatically creates a case in Regpit and prompts the customer to complete the verification.
In Regpit, additional personal and company data is collected and the actual identity check is carried out.
Regpit evaluates the overall risk and returns the result to anny.
If all required data is available and the risk is below the defined threshold, the subscription request is confirmed in anny.
If the risk is too high or required information is missing, the request is not confirmed.
In day-to-day operations, this means: You can have subscription requests checked automatically without separating the compliance decision process from the actual request management in anny.
FAQ
Does every subscription request have to go through Regpit?
That depends on your configuration. The integration is mainly intended for subscription plans where an identity and risk check is required before confirmation.
Where can I see the current status of the check?
You can see the current status in anny on the customer page and on the subscription page in the new identity verification component.
Why is a subscription request not yet confirmed?
Typical reasons include a verification still in progress, missing data, or a result that exceeds the permitted risk threshold.
What happens if the risk is too high?
In this case, the subscription request will not be confirmed in anny. This is intentional and ensures that requests with too high a risk are not automatically approved.
Do admins additionally have to work manually in Regpit?
The compliance review flow runs through Regpit.
Troubleshooting
Problem: The subscription request has been submitted but not yet confirmed.
This may be expected behavior as long as the verification is still in progress, data is missing, or the risk check has not yet returned a result eligible for approval.
Problem: Customers are asking why they are being prompted to verify again.
This often indicates that the Regpit process has not yet been fully completed or that additional information is required.
Problem: A request is not approved even though it appears to be complete.
In addition to the request itself, the Regpit result must also meet the defined conditions. If the overall risk is too high, the request remains unconfirmed.
Problem: The team is unsure where the cause of an open request lies.
First check the verification component on the customer page or subscription page. There, you should be able to see whether the check is still in progress, incomplete, or has not led to a confirmation.