The PayConex API is designed to support asynchronous methodologies, commonly referred to as AJAX. Similar to Transparent Redirect, using AJAX will ensure that the cardholder data is never transmitted back to your webservers or network, and thus may reduce the scope of your PCI compliance requirements by removing transmitted cardholder data from your environment.
|disable_redirect||1||Boolean||Yes||Disabling redirect will override the success_url and decline_url settings, and force the return of transaction response in the format specified by response_format. This setting is required for performing API calls via AJAX.|
Bluefin does not provide a client-side library, as there are numerous client-side libraries that facilitate the passage of POST data to a form handler, and parsing of the response. By far, the most popular such library is jQuery. Bluefin’s AJAX support has been tested to work with modern browsers that support CORS. These browsers include: IE 10+, Firefox 3.5+, Chrome 4+, Safari 4+, iOS Safari 3.2+, Opera 12.1+, Android 2.1+, Chrome for Android 42+, Firefox for Android 37+, IE Mobile 10+, Opera Mobile 12+, and UC Browser for Android 9.9+
<?php // Calculate the hash before rendering page. // Hashed authentication is required for AJAX requests. // API access key should never be visible in source code. // See Appendix: Using HASH for Authenticated Transactions $account_id = "220000000000"; $api_accesskey = "87f519105543418daea2cb6cb9945c7f"; $timestamp = time(); $hash_string = $account_id.",".$api_accesskey.",".$timestamp; $hash_value = hash("sha256",$hash_string); ?>
Updated about 1 year ago