<iframe>tag. This tag creates a frame in your web page and then the checkout page is embedded within that frame.
x_url_completewith 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 Urlto 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_purchaseis true. These have some different ways to process Post-Purchase, it depends on the flow which you choose for implementation.
update-authorizationrequest use Order management API with the same
update-authorizationonce within 10 minutes after the first authorization. Authorization cannot be updated twice.
x_transaction_type(authorization, capture, refund or void) that ShopBase requests.
keyis ShopBase Payment Key. If Provider uses more than 1 ShopBase Payment Key, ShopBase always uses the older one (compared by activated date).
messageis 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
iU44RWxeik, the signing mechanisms would look like this:
x_referenceshould similar to checkout token and order id of ShopBase
x_amountof transaction should matches with the amount of ShopBase
x_resultshould be completed
x_account_idshould match with ShopBase's request