================================================================================ authorizenet ================================================================================ $payment_gateway_switch == 'authorizenet' (25 places in olo) $corp_gateway = 5 // authorizenet=5: authorize_net_profile_id ================================================================================ USAePay ================================================================================ if ($corp_gateway == '1') (9 places in sysfiles, portal, wbapp) $payment_gateway_switch == 'usaepay' (29 places in olo) https://wiki.usaepay.com/developer/soap (in usaepay_functions.php and ztakeout.inc) https://wiki.usaepay.com/developer/phplibrary (in usaepay.php but not used anywhere) ================================================================================ WorldPay ================================================================================ if ($corp_gateway == '2') (10 places in sysfiles, portal, wbapp, egift, super) $payment_gateway_switch == 'worldpay' (29 places in olo) https://developer.worldpay.com/jsonapi/api#orders https://developer.worldpay.com/jsonapi/api#introduction ================================================================================ GLOBALPAY TEST ACCOUNT SETUP ================================================================================ realex@e-hps.com 11:58 AM (12 minutes ago) to realex, me Hi Thomas, Your test account is set up on the Realex system. Please find access details below. If you need any additional services like 3D Secure, RealVault, RealScore or the Alternative Payment Methods enabled on the account, please let me know. Please note that before you can put through test transactions, you will first of all need a shared secret and Realex Merchant ID as below: MerchantID: skooptest Shared Secret: secret Rebate Password: rebate Refund Password: refund RealControl Setup ---------------------------------------- We have a Transaction Management tool called RealControl that is used to manage your transactions. You should have received a separate email from Realex Support titled RealControl registration request which will provide you with more information about how to set this up. Developer Centre ---------------------------------------- Realex Payments provide a Developer Centre to assist you in setting up your online Payment processing. You can use the Developer Centre to access user guides, developer guides and sample code. To access the Developer Centre, please go to https://developer.realexpayments.com. All documentation and sample code is freely available on the Developer Centre. Test Credit Cards are available from the Realex Developer Centre. If you have any questions please let me know. ================================================================================ Global Payments login https://realcontrol.sandbox.realexpayments.com/#/main MerchantID or Client ID: skooptest tkirby YourPassword f5!G6yXP2G1 Passwords must be at least 8 characters in length and contain at least 3 of the following four groups : - Upper-case letter(s) - Lower-case letter(s) - Number(s) - Symbol(s) (BUT THEY DON'T SAY WHICH SYMBOLS, YOU HAVE TO GUESS BY TRIAL AND ERROR - some are not valid) ================================================================================ global payments administration - settings client timezone set to gmt-5 REDIRECT TEXT CONFIGURATION - set to "internet" info text, success text, failure text ================================================================================ Cooper's Cafe Australia https://skooployalty.com.au:8443/ username: admin pw: asd?Mp!bd7 ================================================================================ // dslibrary.inc require_once("$DSROOTPATH/app/Vendor/authorizenet/AuthorizeNet.php"); require_once("$DSROOTPATH/app/Vendor/worldpay/worldpay.php"); require_once("$DSROOTPATH/app/webroot/admin/ztakeout.inc"); $gateway_code = $corp_gateway; // must set $gateway_code for gateway_inc.php require_once($sysfiles."/gateways/gateway_inc.php"); // load payment gateway code ================================================================================ Payment Sense https://www.paymentsense.com/uk/payment-gateway/ important UK ================================================================================ Doshii https://doshii.io/ Australia ================================================================================ SWIFT Society for Worldwide Interbank Financial Telecommunication made support request to spreedly regarding swift transactions 3/7/19 ================================================================================ 1=usaepay 2=worldpay 3=globalpay 4=spreedly 5=authorize.net 6=nuvei 7=paymentsense Which api key is which? It's not apparent from the names, and they are referenced in many places. KEY NAME VALUE IN TABLE USED IN -------------------------------------------------------------------------------- app_api_key WZKXW-26XKV-26XKV-GYI6S-TP7JP wbapp/api/receive_json.php, used 3 times in pos/api pos_api_key 6CPI1APC9BIF6PTTW2UV pos/api/receive_json.php although olo_api_key is used in numerous pos files, and pos_api_key is used in olo_api files!! pos_api_key used also in uniwell api?? also used 3 times in wbapp? olo_api_key 2KX7B-DRSR1-AR23A-HRM3E-HRM3E olo_app_api/receive_json.php olo_api/functions.php -- FOUND "$olo_api_key = $pos_api_key;" in file that creates key values app_olo_api_key 2KX7B-DRSR1-AR23A-HRM3E-HRM3E not used? pos_olo_api_key FEXX5-HGHZA-G33MA-G33MA-ERSAT not used? pos/olo_accept_order.php: olo_api_key = 6CPI1APC9BIF6PTTW2UV olo_api/receive_json.php: pos_api_key = 6CPI1APC9BIF6PTTW2UV olo_api/receive_json.php: olo_api_key = 2KX7B-DRSR1-AR23A-HRM3E-HRM3E olo_api/functions.php: validErrorConfig: olo_api_key = 2KX7B-DRSR1-AR23A-HRM3E-HRM3E IN COMMUNITIES TABLE pos_api_key varchar(50) 6CPI1APC9BIF6PTTW2UV olo_api_key varchar(50) 6CPI1APC9BIF6PTTW2UV CHANGE THIS IN THE DATABASE TABLE TO 2KX7B-DRSR1-AR23A-HRM3E-HRM3E app_olo_api_key varchar(50) 2KX7B-DRSR1-AR23A-HRM3E-HRM3E (*) pos_olo_api_key varchar(50) FEXX5-HGHZA-G33MA-G33MA-ERSAT (*) (*) These two values are created by on_boarding and create_account, but never used. Most significantly they are not used in the olo_api key validation routine. This is weird. The keys do not originate from one single place. starter_index.php generates config-platform.inc (using a fixed string key, not from the database) the olo_api includes config-platform.inc and uses those constants. The /pos api, however, uses the communities table entries (which were NOT used to generate the config-platform.inc values)