We’re noticing that when the Square Payment Form loads with the Cash App Pay button, the browser will continually make a request against the cashapp website every second. What’s a bit disturbing is that when the user leaves the page, such that the Payment Form is no longer displaying, or if they choose a different payment option (such as Apple Pay, Google Pay, or Credit Card), the requests do not stop.
We had initially followed the implementation as proposed in the example documentation, which did not list any
destroy calls, after we
attach the elements to their respective
Elements. However, even when we call
destory, the API calls persist.
Furthermore, if the user leaves the
Payment Form, and returns in the same
SPA session, the
Cash App Pay button will not load citing the message that it needs to be
destroyed before being
created again. Again, this is despite the fact that we’re calling the
destroy method on the various
Payment Element Options.
Is this a bug we are encountering? Is the behavior somehow different on the Sandbox than the Production environment when it comes to destroying these elements, or is there something I’m missing.
Please let me know,
~ Theodore Schnepper