On balance, it's quite difficult to simplify the Anubis process - but this should explain things a little - select a method below.
| your website | anubis server | your server |
|---|---|---|
| Anubis serves its embed on your website | ||
| your user attempts to submit a form on your website | ||
| Anubis tests the user's response against its API to initially validate the response | ||
| on success, your website submits the form to your server | ||
| your server checks the response key using your secret key | ||
| Anubis returns the ultimate success/fail status of the challenge | ||
| your server behaves accordingly depending on the result | ||
| on success, your website submits the form to the Anubis no-code redirect | ||
| if the response was fully-passed, Anubis redirects the user to the correct page on your website | ||
| if you set up a callback, Anubis will post the data to your server, returning the user to the success page |