“Three valid aviation-data attempts hit the same payment-state error”

I tested the AviationStack via Tempo MPP integration on July 17, 2026 with three valid $0.005 calls. I requested aircraft types twice, then tried a practical route lookup for SFO to JFK with a five-result limit.

GET https://aviationstack.mpp.tempo.xyz/v1/routes?dep_iata=SFO&arr_iata=JFK&limit=5

Every attempt reached the advertised charge challenge and then failed in the same sponsored-payment state.

Sponsored transaction from this sender is already in flight.

No aircraft types, route records, pagination metadata, request ID, debit, or other provider output arrived. This review is about the Tempo MPP integration, not AviationStack's standard API. Repeating the failure across different valid endpoints showed a persistent integration problem rather than a bad query.