I agree with Mike... using the WebBrowser control and loading the IFrame in the WebBrowser control is the only way to do it.  I recommend upgrading to from PB 2019 to PB 2019 R3 so you have the secure version of WebBrowser control for PCI compliance.  Older versions of PB are not going to be secure for PCI compliance.

Hi Angelo;

  PowerServer would have nothing to do with your iFrame interaction. The PS Server would only broker your App's data access. So the key question would be what PCI compliant API's exist to interact with iFrame from the PB App (whether it's C/S, PowerClient or PowerServer based) based on C++. Since I don't know iFrame, it can't answer that part of the question. Probably a good question for the iFrame folks to guide you further.

  Now if your Web API's were built with SnapDevelop where you would be coding in pure C#, that could be a good question. Again though, the iFrame people should be able to guide you with a C# DotNet API requirements.  

  Nite that Appeon PB now supports direct C# DotNet assembly consumption in your PB App. So the same iFrame API might also suffice when called from your PB App as well. HTH 

Regards ... Chris 

My thought is to use the webbrowser control, which has been updated in R2, since you need to be able to get the return token.  using an embedded browser like that however, may not be PCI compliant. 

edit: actually, i'm pretty sure it isn't pci compliant since the browser is technically under your control.  

The ideal is to pop up the users default browser - but then you need to get the returned results into your ps app.