A technical analysis of MTN's payment API callback behavior, revealing that providerCallbackHost functions as an allow-list restricting where callbacks can be sent, not a delivery destination. The author documents critical design implications: callbacks arrive unsigned and unauthenticated, lack referenceId fields, and may retry after successful receipt, requiring systems to treat timeouts as unknown states requiring reconciliation rather than definitive failures.