Airwallex

Discussion around Airwallex over the recent four-week window was heavily dominated by bug reports and integration frustrations, with complaints outpacing praise by a wide margin. Commenters raised issues spanning incorrect import paths in the React Native SDK, cached payment intent states causing unexpected behavior in Android dialogs, and Google Pay failing in production environments due to merchant ID configuration limitations. Several mentions pointed to missing or non-functional payment method support, including FPS not appearing in the Drop-In picker despite being activated on the dashboard. The overall tone from developers was one of persistent friction rather than outright hostility, but the volume of technical grievances gave the conversation a noticeably exhausted character.

Sentiment shifted notably across the tracked window. Discussion opened at a relatively stable and mildly positive level through late November and into early December, with scores holding steady before a first drop in late December. After a brief and isolated rebound in late April that stood out sharply against the surrounding trend, sentiment fell steeply into mid-May, reaching its lowest recorded points in the window. The most recent data point shows a partial recovery, though still well below earlier baselines, suggesting the rebound is tentative rather than sustained.

Where opinion divided most clearly was around SDK flexibility. A subset of commenters expressed a need for re-initialization support to handle dynamic locale changes, framing this as a missing feature that blocks real-world use cases. Others focused on specific payment method gaps, such as Alipay HK integration, which carried a more neutral feature-request tone. The small number of positive signals, touching on integration quality and specific features, were isolated and did not meaningfully offset the complaint volume.

The gap between the current pulse score and the previous score reinforces a broader downward drift in how developers are publicly discussing the product. Discussion suggested that SDK-level reliability and configurability are the primary pressure points shaping tone right now.