Incompatibility with Systempay ?

  • Resolved Olivier

    (@pumpk1in)


    3 years, 1 month ago

    Hi,

    I had to disable BBQ for the first time on a specific website using WooCommerce and Systempay Gateway for payments.

    With BBQ, the customer gets a 403 error while returning to the website after payment. BBQ seems to not like the GET parameters.

    The URL the customer get after payment is : (I replaced critical customer and payment data with “xxxxx”)

    https://www.shopdomain.com/?wc-api=WC_Gateway_Systempay&vads_amount=100&vads_auth_mode=FULL&vads_auth_number=xxxxxxx&vads_auth_result=00&vads_capture_delay=0&vads_card_brand=CB&vads_card_number=XXXXXXXXXXX&vads_payment_certificate=xxxxxxxxxxxxxxxxx&vads_ctx_mode=PRODUCTION&vads_currency=978&vads_effective_amount=100&vads_effective_currency=978&vads_site_id=xxxxxxxx&vads_trans_date=20211004141402&vads_trans_id=xxxxxxx&vads_trans_uuid=a50bxxxxxxxxxxxxxxxaf8c1&vads_validation_mode=0&vads_version=V2&vads_warranty_result=YES&vads_payment_src=EC&vads_order_id=xxxxx&vads_cust_email=xxxxxxxt%40gmail.com&vads_cust_id=3&vads_cust_name=xxxxxx+xxxxx&vads_cust_first_name=xxxxxx&vads_cust_last_name=xxxxxx&vads_cust_address=26+CH+xxxxxx&vads_cust_zip=13600&vads_cust_city=xxxxxxx&vads_cust_country=FR&vads_cust_phone=xxxxxxxx&vads_contrib=WooCommerce_2.x-5.x_1.9.4%2F5.8.1_5.7.1%2F7.4.21&vads_cust_state=&vads_ship_to_name=xxxxxxx+xxxxxx&vads_ship_to_street=26+CH+XXXXXXX&vads_ship_to_city=xxxxxxxx&vads_ship_to_zip=xxxxx&vads_ship_to_country=FR&vads_ship_to_first_name=xxxxxxx&vads_ship_to_last_name=xxxxxxx&vads_tid=xxxx&vads_sequence_number=1&vads_acquirer_network=CB&vads_contract_used=xxxxxxx&vads_trans_status=AUTHORISED&vads_expiry_month=xx&vads_expiry_year=xxxx&vads_bank_code=xxxxxxx&vads_bank_label=xxxxxxxxxxx&vads_bank_product=F&vads_pays_ip=FR&vads_presentation_date=20211004141403&vads_effective_creation_date=xxxxxxxx&vads_occurrence_type=UNITAIRE&vads_operation_type=DEBIT&vads_result=00&vads_extra_result=&vads_card_country=FR&vads_language=fr&vads_brand_management=%7B%22userChoice%22%3Afalse%2C%22brandList%22%3A%22CB%7CVISA%22%2C%22brand%22%3A%22CB%22%7D&vads_action_mode=INTERACTIVE&vads_payment_config=SINGLE&vads_page_action=PAYMENT&vads_ext_info_blog_id=0&vads_ext_info_order_key=wc_order_xxxxxxxxjZ&vads_threeds_enrolled=Y&vads_threeds_auth_type=CHALLENGE&vads_threeds_eci=xxx&vads_threeds_xid=&vads_threeds_cavvAlgorithm=&vads_threeds_status=Y&vads_threeds_sign_valid=&vads_threeds_error_code=&vads_threeds_exit_status=10&vads_threeds_cavv=xxxxxxxxAAxxxxAAAAAA%3D&signature=lUK2zjlgAxxxxxxxxxZRZbxxxxxxxx%3D

    Anything we can do to avoid that behavior ?

    Thanks !

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Jeff Starr

    (@specialk)

    By default BBQ Firewall (free version) blocks excessively long URL requests. Any request or referrer sporting a request string longer than 2,000 characters is blocked. That is the reason for the denied request. You can disable the long-request blocking by adding the following code to your site:

    function bbq_long_requests($enable) { return false; }
add_filter('bbq_long_requests', 'bbq_long_requests');

    After save and upload, BBQ will no longer block any requests due to length. More infos here.

    Update: this code needs added via plugin, won’t work if added via theme functions. You can download the plugin version via the above link.

    • This reply was modified 3 years, 1 month ago by Jeff Starr.
    Thread Starter Olivier

    (@pumpk1in)

    It seems that this is not working on my end.
    BBQ is still blocking the request. Strange

    • This reply was modified 3 years, 1 month ago by Olivier.
    Plugin Author Jeff Starr

    (@specialk)

    How are you adding the code?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Incompatibility with Systempay ?’ is closed to new replies.