# Help Center ### What is FlyCode
| what-makes-flycode-different | 1.png |
| getting-started | 2.png |
| results-and-roi | 3.png |
| what-is-involuntary-churn | 4.png |
| causes-and-risks | 5.png |
| flycodes-approach-to-churn | 6.png |
| integration-considerations | 7.png |
| when-and-how-payments-are-retried | 8.png |
| reducing-churn-from-failed-payments | 9.png |
| coordinating-messaging-with-recovery | 10.png |
| connecting-flycode-to-stripe | 16.png |
| what-flycode-adds-to-stripe | 17.png |
| going-further-with-flycode | 18.png |
| recovery-performance | 19.png |
| whats-different-behind-the-scenes | 20.png |
| platform-fit-and-compatibility | 21.png |
| what-you-keep-and-gain-if-you-switch | 22.png |
| compatibility-and-app-support | 23.png |
| setup-and-requirements | 24.png |
| hard-declines-and-backup-logic | 25.png |
| email-behavior-and-deliverability | 26.png |
| messaging-customization | 27.png |
| delivery-strategy | 28.png |
| system-integration | 29.png |
| product-overview | 30.png |
| functionality | 31.png |
| reporting | 32.png |
| feature-overview | 33.png |
| platform-fit-and-performance | 34.png |
| monitoring-and-reporting | 35.png |
| regulatory-rules | 36.png |
| legal-and-tracking-requirements | 37.png |