How mam-main talks to APNs: HTTP/2 transport via MAM_IosPushSender, .p8 key + JWT auth via MAM_ApnsTokenProvider, payload building via MAM_IosPayloadBuilder, and the separate VoIP path via MAM_IosVoipPushSender.
How mam-main talks to FCM v1: OAuth2 service-account JWT auth via MAM_FirebaseJwtSigner, payload building via MAM_AndroidPayloadBuilder, send via MAM_AndroidPushSender. The deprecated server-key API is not used.
Why mam-main uses FastCron instead of wp-cron.php, how mam_setcron_manager schedules jobs through the FastCron REST API, and the AJAX endpoint mam_setcron_processor that pings on every tick.
How mam-main hands off iOS / Android builds to the WPMAM Fastlane CI: account-code verification, mam_fastlane_settings filter, the publish endpoint, and the fire-and-forget submit pattern.
How MAM_Account_Code_Manager owns the local-app-account_code option, the enrollment server handshake, the transient cache, and the graceful-degradation hooks for enrollment-server unreachability.
Can't find the answer you're looking for? Don't worry we're here to help!