<iframe> tag. This tag creates a frame in your web page and then the checkout page is embedded within that frame.x-www-form-urlencoded format.x_url_complete with GET method and all required parameters. ShopBase will validate the data and create the Order.x_url_callback. It informs ShopBase that the payment has completed with the same response parameters as when it was redirected. It also ensures that the Order will be created even if the buyer goes offline before being redirected to ShopBase.Iframe Url to block Payment method on the checkout page.x_url_callback. It informs ShopBase that the payment has completed with the same response parameters when posting the message on iframe. It also ensures that the Order will be created even if the buyer loses the connection before the ShopBase Server receives the payment information.x_post_purchase is true. These have some different ways to process Post-Purchase, it depends on the flow which you choose for implementation.x_reference and x_post_purchase is true.update-authorization request use Order management API ​with the same x_reference and x_post_purchase is true.update-authorization once within 10 minutes after the first authorization. Authorization cannot be updated twice​.x_account_id Required.x_amount Required.x_reference Required.x_shop_name Required.x_test Required.x_url_callback Required.x_url_cancel Required.x_url_complete Required.x_post_purchasex_purchase_items
x_customer_billing_address1x_customer_billing_address2x_customer_billing_cityx_customer_billing_companyx_customer_billing_phonex_customer_billing_statex_customer_billing_zipx_account_id Required.x_amount Required.x_amountx_gateway_reference Required.x_reference Required.x_referencex_transaction_type Required.authorization, capture, refund, voidx_result Required.completed, failedx_test Required.x_testx_timestamp Required.x_messagex_error_codex_intent Required.x_iframe_heightx_account_id Required.x_amount x_reference Required.x_gateway_reference Required.x_test Required.x_url_callback Required.x_transaction_type Required.update-authorization, capture, refund, voidx_invoicecapturex_refund_reasonrefundx_gateway_reference Required.x_reference Required.x_referencex_transaction_type Required.authorize, capture, void, and refund.x_result Required.completed or failedx_timestamp Required.x_messagex_error_codex_transaction_type (authorization, capture, refund or void) that ShopBase requests.x_account_id Required.x_reference Required.x_transaction_typex_gateway_reference Required.x_test Required.x_transaction_type Required.authorization, capture, refund, voidx_result Required.completed, failedx_gateway_credentials Required.x_result Required.x_account_id Required.x_gateway_credentials Required.x_messagex_error_codex_url_callback param.x_account_id Required.x_amount Required.x_amountx_gateway_reference Required.x_reference Required.x_referencex_transaction_type Required.authorization, capture, refund, voidx_result Required.completed, failedx_test Required.x_testx_timestamp Required.x_messagex_error_codekey is ShopBase Payment Key. If Provider uses more than 1 ShopBase Payment Key, ShopBase always uses the older one (compared by activated date). message is a string of all key-value pairs that start with x_ prefix, sorted alphabetically and concatenated without separators.x_signature. Make sure to use case-insensitive comparison when verifying the provided x_signature values.iU44RWxeik, the signing mechanisms would look like this:X-Signature of request.x_reference should similar to checkout token and order id of ShopBasex_amount of transaction should matches with the amount of ShopBase x_result should be completedx_test, x_account_id should match with ShopBase's request