App Settings
The App Settings page contains all configuration options for your app. Changes are saved automatically as you make them.
Status & Platforms
Section titled “Status & Platforms”App Status
Section titled “App Status”Toggle your app between Active and Inactive:
- Active: Accepts referral attribution requests
- Inactive: Rejects all
/deferand/claimrequests
Platforms
Section titled “Platforms”Select which platforms your app supports:
- iOS — Apple App Store
- Android — Google Play Store
- Both — Cross-platform app
General Settings
Section titled “General Settings”Expand the General accordion to access these settings:
Attribution Mode
Section titled “Attribution Mode”Choose how referrals are matched to installs:
| Mode | Description | Best For |
|---|---|---|
| Code | Requires explicit claim code from /defer-preflight | Maximum accuracy, user-confirmed attribution |
| Window | Time-based matching within 10 minutes | Frictionless UX, best-effort matching |
CORS Origins
Section titled “CORS Origins”If you’re calling the BitEasy API from a web app, add your domain(s) here:
https://yourapp.comhttps://staging.yourapp.comComma-separated list of origins allowed to make requests.
Minimum Payout
Section titled “Minimum Payout”Set the minimum amount (in cents) before a partner payout is processed:
- Default: $5.00 (500 cents)
- Partners won’t receive payouts until their earnings exceed this threshold
Attestation
Section titled “Attestation”Expand the Attestation accordion to configure app attestation:
Firebase App Check
Section titled “Firebase App Check”Ensure that /claim requests are coming from your legitimate app — not modified versions, emulators, or scripts:
- Select Firebase as the provider
- Enter your Firebase Project Number (found in Firebase Console > Project Settings)
For the full setup guide including Firebase Console configuration, mobile SDK integration, and troubleshooting, see Firebase App Check Setup Guide.
No Attestation
Section titled “No Attestation”Select None to disable attestation (not recommended for production).
In-App Purchase Provider
Section titled “In-App Purchase Provider”Expand the IAP Provider accordion to configure how BitEasy receives purchase events.
RevenueCat
Section titled “RevenueCat”The simplest integration — BitEasy receives webhooks from RevenueCat:
- Select RevenueCat as the provider
- Enter your Webhook Authorization Secret
- Configure the webhook URL in RevenueCat dashboard (see Webhooks Setup)
Apple (Direct)
Section titled “Apple (Direct)”For direct Apple App Store Server Notifications:
| Field | Description |
|---|---|
| Bundle ID | Your app’s bundle identifier |
| App Apple ID | Numeric App Store ID |
| Issuer ID | From App Store Connect |
| Key ID | Your private key identifier |
| Encoded Key | Base64-encoded private key |
Google (Direct) - Coming Soon
Section titled “Google (Direct) - Coming Soon”For direct Google Play Real-time Developer Notifications:
| Field | Description |
|---|---|
| Package Name | Your app’s package name |
| Pub/Sub Topic | Your Google Cloud Pub/Sub topic |
Danger Zone
Section titled “Danger Zone”The Archive App section lets you archive the app. See Managing Apps for details.
Next Steps
Section titled “Next Steps”- Stripe Integration — Connect Stripe for payouts
- Webhooks Setup — Configure IAP webhooks