Response Output:
How to use the Demo:
Tokenization is the process of replacing sensitive payment data with a non-sensitive algorithm-generated string called a token. Each time a card or bank account number is sent with a transaction, the iFrame response will include a token represented by xToken. As a merchant’s PCI-compliance scope is greatly increased when storing sensitive data, best-practice is to store the token in your database instead of the sensitive data and use the token for follow-up transactions. With this approach, if a data breach occurs on your local system, sensitive data will not be at risk. Insert the iFrame in your page
iFrame Url: https://iframe.icheckgateway.com/iFrameCC.aspx

    <iframe id="iFrameCC" name="iFrameCC" src="https://iframe.icheckgateway.com/iFrameCC.aspx?appId=123456&appSecret=123456&custId=123456&firstName=John&lastName=Doe&street1=1st+street&
    css=payment{background:white;}" frameborder="0" scrolling="no" width="1000" height="400"></iframe>
Try It Yourself
Link to Examples of Forms that could be used by the Merchant before the iFrame:
Call Parameters Definition:
Variable Required Description Validation Sample
Payment Call Parameters Definition:
Variable Required Description Validation Sample
Response Parameters Definition:
Variable Description Sample
Set iFrame Configuration based on use case:
You can set these credentials to test the 2 operations provided by iFrame: Save Token and Process Transaction
  • Process Transaction and Generate Token
    • appId = 123456
    • appSecret = 123456
  • Generate Token
    • appId = 222222
    • appSecret = 222222
  • Process Transaction
    • appId = 333333
    • appSecret = 333333
Dynamic Example to Run:

See the Pen iCG iFrame by Jason Estes (@amazingjre) on CodePen.