# Legal obligations from Rapyd when going live in production

**URL:** https://community.rapyd.net/t/legal-obligations-from-rapyd-when-going-live-in-production/58135
**Category:** 🙋🏽‍♀️🙋🏽‍♂️ Ask Questions
**Created:** [November 18, 2022, 9:24am UTC](https://community.rapyd.net/t/legal-obligations-from-rapyd-when-going-live-in-production/58135 "2022-11-18T09:24:32Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![dlupo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.rapyd.net/dlupo/32/901_2.png) [@dlupo](https://community.rapyd.net/u/dlupo)
#### Post date: [November 18, 2022, 9:24am UTC](https://community.rapyd.net/t/legal-obligations-from-rapyd-when-going-live-in-production/58135/1 "2022-11-18T09:24:32Z")

</div>

We are planning to go live in production by the end of the month in a close alpha test. I can’t find any obligations from Rapyd in the docs, by obligations I mean _things that we need to do before going live_, besides having a production account of course.

For example, Mangopay requires us to publish their logo and T&C on our site, and an opt-in that new users need to accept before onboarding.  
Treezor for example requires us to fill an IDS file with a few live checks of our application.

Can anybody point me to a document related to this?

Thanks!

---

<div class="post-metadata">

### Author: ![Community\_Team](https://avatars.discourse-cdn.com/v4/letter/c/46a35a/32.png) [@Community\_Team](https://community.rapyd.net/u/Community_Team)
#### Post date: [November 18, 2022, 11:25pm UTC](https://community.rapyd.net/t/legal-obligations-from-rapyd-when-going-live-in-production/58135/2 "2022-11-18T23:25:06Z")

</div>

Thanks @dlupo, here is the legal hub [https://www.rapyd.net/security-compliance/](https://www.rapyd.net/security-compliance/)

Most relatable resource would be [https://www.rapyd.net/security-compliance/rapyd-services-agreement/](https://www.rapyd.net/security-compliance/rapyd-services-agreement/)