Disabling security for iFrame is restricting a card payment processor

If security restrictions are blocking automation, the best course of action is to explore alternative solutions rather than trying to bypass security measures.

1. TestComplete can access iFrames, but only if the browser security settings allow it. By default, browsers enforce same-origin policy, which prevents cross-origin iFrame interaction. To bypass this, users often disable security settings like --disable-web-security and --disable-site-isolation-trials. If the payment processor has updated its security measures, it may now detect these settings and block interactions.
2. TestComplete itself cannot override browser security policies. The best approach is to check if One Inc provides an alternative way to interact with the payment processor, such as an API or a different integration method.
3. Using keyboard interactions (Keys Method) is a possible workaround, but it may not be reliable for complex interactions within an iFrame. If the iFrame content responds to key presses, you might be able to send keyboard inputs directly to it.

https://support.smartbear.com/testcomplete/docs/reference/test-objects/members/common-for-sys-desktop-pda/keys-method-sys-desktop-object.html 

P.S. if you like a post give credit and click like, and if it addresses your issue help the community and mark it as a solution.