{"id":437,"date":"2024-08-08T18:48:20","date_gmt":"2024-08-08T18:48:20","guid":{"rendered":"https:\/\/lddpay.com\/?post_type=docs&p=437"},"modified":"2025-04-26T06:34:49","modified_gmt":"2025-04-26T06:34:49","password":"","slug":"checkout-integration","status":"publish","type":"docs","link":"https:\/\/lddpay.com\/zh\/docs\/checkout-integration\/","title":{"rendered":"Checkout Integrations"},"content":{"rendered":"

Checkout Integrations<\/h1>\n\n\n\n

Version: 6.4.4
Released: 2025\/03\/01<\/p>\n\n\n\n

Copyrighted by lddPay<\/p>\n\n\n\n

Introduction<\/h2>\n\n\n\n
\n\n\n\n

This document describes the Checkout integration procedures between Checkout service and the website for e-commerce merchants.
To make your integration easier, please download collection and try it out:
Postman Collection<\/ins><\/a><\/p>\n\n\n\n

General Information<\/h2>\n\n\n\n
\n\n\n\n

Checkout service is a fast and easy way to create a secure payment page. It allows collecting and submitting payments and sending them for processing.<\/p>\n\n\n\n

To use the Checkout service on the site you have to perform integration. Checkout integration provides a set of APIs that allow customizing payment processing for the business. These protocols implement acquiring payments (purchases) using specific API interaction with the merchant websites.<\/p>\n\n\n\n

The API requires request data as json string data and responds also with json string data.<\/p>\n\n\n\n

Checkout process<\/h3>\n\n\n\n

Checkout payment flow is shown below.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

When a Customer wants to make a purchase on your site the following happens:<\/p>\n\n\n\n

    \n
  1. Customer places an order and initiates payment on the site.<\/li>\n\n\n\n
  2. Site confirms the order and sends the payment processing request to the Checkout system with information about the order, payment and hash.<\/li>\n\n\n\n
  3. Checkout system validates the request and sends to the site the response with the redirect link.<\/li>\n\n\n\n
  4. The site redirects the Customer on the Checkout page by redirect link.<\/li>\n\n\n\n
  5. Customer selects the payment method, enters the payment data and confirms the payment. The payment method will be specifying automatically If only one method is available.<\/li>\n\n\n\n
  6. The payment processes at Payment Gateway.<\/li>\n\n\n\n
  7. Payment Gateway sends a callback to the site with the payment result.<\/li>\n\n\n\n
  8. The payment result is shown to the Customer.<\/li>\n<\/ol>\n\n\n\n

    The payment could be declined in case of invalid data detection.<\/p>\n\n\n\n

    Protocol Mapping<\/h3>\n\n\n\n

    It is necessary to check the existence of the protocol mapping before using the Checkout integration. Merchants can\u2019t make payments if the CHECKOUT protocol is not mapped.<\/p>\n\n\n\n

    Customer return after payment<\/h3>\n\n\n\n

    After completing the payment, the payer will be returned to the URL specified in the Authentication request in the “success_url” and “cancel_url” parameters. If you need to get additional parameters in the return URLs, you should configure it in the Protocol Mappings modules by enabling the “Return parameters” attribute. In that case, “success_url” and “cancel_url” will contain the following data:<\/p>\n\n\n\n

    Parameter<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
    payment_id<\/code><\/td>Payment ID
    Example:<\/strong> dc66cdd8-d702-11ea-9a2f-0242c0a87002<\/td><\/tr>
    trans_id<\/code><\/td>Transaction ID
    Example:<\/strong> dc66cdd8-d702-11ea-9a2f-0242c0a87002<\/td><\/tr>
    order_id<\/code><\/td>Order ID
    Example:<\/strong> order-1234<\/td><\/tr>
    hash<\/code><\/td>Special signature, used to validate data. Addition in Signature section.
    Must be SHA1 of MD5 encoded string (uppercased): payment_public_id + order.number + order.amount + order.currency + order.description + merchant.pass<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    \u26a0\ufe0f Pay attention<\/strong><\/p>\n\n\n\n

    \n

    that for “cancel_url”, the payer’s return to the merchant with parameters is possible only after the decline has happened and the payer has closed the payment form (not the browser tab). If the payer closes the payment form without initiating the payment (pressing the PAY button), the redirection to “cancel_url” occurs without passing additional parameters.<\/em><\/p>\n<\/blockquote>\n\n\n\n

    DMS mode<\/h3>\n\n\n\n

    If you need to use Checkout integration to work with payments in DMS-mode (two-step payments), you should set the corresponding MID configuration in the admin panel. Specify DMS-mode for the MID attribute. In this case, the payment request will be processed as an authorization stage for DMS-mode. The capture requests will be generated and gathered in the queue. You could monitor and manage the capture request queue via the admin panel as well. For detailed information, please contact your administrator.<\/p>\n\n\n\n

    Checkout page description<\/h3>\n\n\n\n
    \n\n\n\n

    Checkout page is shown to the Customer after a payment initiation. There are the fields to enter the payment data.<\/p>\n\n\n\n

    Fields and Validation<\/h3>\n\n\n\n

    The list of the fields on the Checkout page depends on the request parameters and the specified payment method.<\/p>\n\n\n\n

    Your customers will not see the fields if the acquirer does not need the information that is transmitted in them. For example, if an alternative payment method is specified, the card data is not displayed on the Checkout page.<\/p>\n\n\n\n

    As well, pay attention to the conditional fields such as e-mail or billing address. If the e-mail and billing address (data object) parameters are specified in the request, the Checkout page will not contain them.<\/p>\n\n\n\n

    Additional fields can also be displayed if a payment method is selected that requests additional data from the Customer.<\/p>\n\n\n\n

    The Checkout page has the fields validation. In case of the invalid data the error message will be shown and the field will be highlighted.<\/p>\n\n\n\n

    The list of the general fields and possible errors on the Checkout page is below:<\/p>\n\n\n\n

    Fields<\/strong><\/th>Type<\/strong><\/th>Limitations<\/strong><\/th>Error<\/strong><\/th><\/tr><\/thead>
    Card number<\/code><\/td>Integral<\/em><\/td>Lun algorithm, length 14-19 numbers<\/td>Invalid card number<\/td><\/tr>
    Expir\u0443 Date<\/code><\/td>Date<\/em><\/td>2-2 numbers (in the format mm-yy),
    after today’s date<\/td>    		The expiration date of card is expired
    and not valid.<\/td><\/tr>
    Security code<\/code><\/td>Integral<\/em><\/td>Up to 4 characters<\/td>Invalid security code<\/td><\/tr>
    Name on card<\/code><\/td>String<\/em><\/td>Up to 32 characters<\/td>The name on card field
    Must contain at least 2 words: first name and last name. Allowed special characters: hyphens, apostrophes, diacritics<\/td><\/tr>
    Country<\/code><\/td>List<\/em><\/td>2-letters code<\/td>Country is required.
    Please enter a valid Country<\/td><\/tr>
    State\/Region<\/code><\/td>String<\/em>
    List<\/em> – for USA,
    Canada, Australia,
    Japan, India<\/td>    		<\/td><\/td><\/tr>
    City<\/code><\/td>String<\/em><\/td>Up to 32 characters<\/td>City is required.
    Please enter a valid City<\/td><\/tr>
    Address line<\/code><\/td>String<\/em><\/td>Up to 32 characters<\/td>Address line is required.
    Please enter a valid Address line<\/td><\/tr>
    Zip code<\/code><\/td>String<\/em><\/td>Up to 32 characters<\/td>Zip code is required.
    Please enter a valid Zip code<\/td><\/tr>
    Phone number<\/code><\/td>String<\/em><\/td>Up to 32 characters<\/td>Phone number is required.
    Please enter a valid Phone number<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Pre-routing<\/h3>\n\n\n\n

    To make payment method choice easier for the Customer, pre-routing is provided on the Checkout.<\/p>\n\n\n\n

    The functionality allows you to set up matches in the admin panel via the Custom routing module, which will determine the list of payment methods suitable for the current payment.<\/p>\n\n\n\n

    This way, you can restrict your Customers from randomly choosing a payment method that is not available in their region, for example. This will help you to increase the number of successful payments and reduce the risk of declined transactions.<\/p>\n\n\n\n

    Note that if the Authentication request contains a list of the payment methods in the methods<\/code> array, then the pre-routing configurations will be ignored.<\/p>\n\n\n\n

    Card data tokenization<\/h3>\n\n\n\n

    For regular customers, we have made the payment page even more convenient and simple.<\/p>\n\n\n\n

    You can save the customer’s card data so that they can reuse it for future payments.<\/p>\n\n\n\n

    To do this, you need to send the req_token = true<\/code> parameter in the Authentication request. And then, in the callback, you will receive a card token.<\/p>\n\n\n\n

    Use the token when sending the next Authentication request and your client will see anonymized card details on the payment form, which will greatly simplify the payment process.<\/p>\n\n\n\n

    Web information<\/h3>\n\n\n\n

    Checkout service gathers information about browser, which the Customer uses.<\/p>\n\n\n\n

    When the Customer is on the Checkout page, the service gets the data about the Customer’s OS, browser, and browser language. That information is sent to the acquirer in some cases.<\/p>\n\n\n\n

    iFrame option<\/h3>\n\n\n\n

    You can use iFrame option to show Checkout page on your domain. All you need is just to past in the code redirect url received in the response to the Authentication request.<\/p>\n\n\n\n

    Please follow the example:<\/p>\n\n\n\n

    <iframe src=redirect_url height=\"600\" width=\"300\"><\/iframe><\/code><\/pre>\n\n\n\n
    Note that screen size can be adjusted according to your requirements.<\/p>\n\n\n\n
    Important:<\/em> cross-domain requests are prohibited by security policy of our service.<\/p>\n\n\n\n
    \u26a0\ufe0f Pay attention<\/strong><\/p>\n\n\n\n
    \n
    By adding our Checkout Payment Page to the iframe on your site, ensure you ALLOW ACCESS TO COOKIE STORAGE.<\/em>
    This is required to avoid issues when redirecting the payer back to your site, such as after 3DS authentication. If you prohibit the storage of third-party data in your cookies, you will prevent the identification of the payer after returning from 3DS. This can cause interruptions in the payment session.<\/em><\/p>\n<\/blockquote>\n\n\n\n
    Page Customization<\/h3>\n\n\n\n
    The administration service provides the ability to stylize the Checkout page in accordance with the preferences of the merchant. The action is available for the authorized users only. To customize the payment page you need:<\/p>\n\n\n\n
      \n
    1. Click the \u201cConfiguration \u2192 Branding\u201d item on the menu bar. The settings are displayed in the work area.<\/li>\n\n\n\n
    2. Select a page template to make changes.<\/li>\n\n\n\n
    3. Change the settings:\n
        \n
      1. login icon selection;<\/li>\n\n\n\n
      2. color selection for the following items:\n
          \n
        1. heading;<\/li>\n\n\n\n
        2. background;<\/li>\n\n\n\n
        3. buttons;<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n\n\n\n
        4. Click the \u201cSubmit\u201d button to apply the settings. The selected settings will be displayed to the Customers on the Checkout page.<\/li>\n<\/ol>\n\n\n\n
          Authentication request parameters<\/h2>\n\n\n\n
          \n\n\n\n
          The merchant submits an authorization request and as a result of successful response receives the redirect_url<\/code> – link on the Checkout page.<\/p>\n\n\n\n
          \/api\/v1\/session<\/code><\/pre>\n\n\n\n
          The authentication performs when the payment is initiated.<\/p>\n\n\n\n
          You need to send an authentication POST request in JSON format on Checkout form URL (CHECKOUT_URL) to start checkout process for the Customers. As a result of the authentication request you will receive the following:<\/p>\n\n\n\n
            \n
          • An authentication session is created with a unique identifier (Session ID). The session expires after one hour.<\/li>\n\n\n\n
          • A link is generated to redirect to the Checkout page: one link corresponds to one payment. The link becomes invalid after a successful payment. The authentication request parameters are below.<\/li>\n<\/ul>\n\n\n\n
            If DMS-mode (two-stages payment) is available, after successful authentication it is necessary to capture. The capture would be performed automatically according to the settings or you can do it manually in the admin portal.<\/p>\n\n\n\n
            Request Parameters<\/h3>\n\n\n\n
            Parameter<\/strong><\/th>Type<\/strong><\/th>Mandatory, Limitations<\/strong><\/th>Description<\/strong><\/th><\/tr><\/thead>
            merchant_key<\/code><\/td>String<\/em><\/td>Required<\/td>Key for Merchant identification
            Example:<\/strong> xxxxx-xxxxx-xxxxx<\/td><\/tr>
            operation<\/code><\/td>String<\/em><\/td>Required<\/td>Defines a payment transaction
            Possible values:<\/strong> purchase, debit, transfer
            Send the \u201cpurchase\u201d value so that the payment page for sale initiation will be shown to the customer.
            Send the \u201cdebit\u201d value so that the payment page for debit initiation will be shown to the customer.
            Send the \u201ctransfer\u201d value so that the payment page for transfer initiation will be shown to the customer.
            Example:<\/strong> purchase<\/td><\/tr>
            methods<\/code><\/td>Array<\/em><\/td>Optional<\/td>An array of payment methods. Limits the available methods on the Checkout page (the list of the possible values in the Payment methods section). In the case of parameter absence, the pre-routing rules are applied. If pre-routing rules are not configured, all available payment methods are displayed.
            Condition:<\/strong> for purchase operation only
            For purchase and debit operations.
            Example:<\/strong> card, paypal, googlepay<\/td><\/tr>
            session_expiry<\/code><\/td>Integer<\/em><\/td>Optional
            Values from 1 to 720 min<\/td>            		Session expiration time in minutes.
            Default value = 60.
            Could not be zero.
            Example:<\/strong> 60<\/td><\/tr>
            success_url<\/code><\/td>String<\/em><\/td>Required
            Valid URL
            max: 1024<\/td>            		URL to redirect the Customer in case of the successful payment
            Example:<\/strong> https:\/\/example.domain.com\/success<\/a>
            The return of additional parameters can be configured for success_url. See the \u201cCustomer return after payment\u201d section for details.<\/td><\/tr>
            cancel_url<\/code><\/td>String<\/em><\/td>Optional
            Valid URL
            min: 0 max: 1024<\/td>            		URL to return Customer in case of a payment cancellation (\u201cClose\u201d button on the Checkout page). The logic of redirection on \u201ccancel_url\u201d could be configured in the admin panel (Configuration -> Protocol Mappings section): use the \u201cMaximum count declines\u201d field to set the payment failed attempts quantity before redirection. For example, if the field value is set to “1”, then after the first declined attempt, a payer will be redirected to “cancel_url.”
            Example:<\/strong> https:\/\/example.domain.com\/cancel<\/a>
            The return of additional parameters can be configured for cancel_url. See the \u201cCustomer return after payment\u201d section for details.<\/td><\/tr>
            expiry_url<\/code><\/td>String<\/em><\/td>Optional
            Valid URL
            min: 0 max: 1024<\/td>            		URL where the payer will be redirected in case of session expiration
            Example: <\/strong>https:\/\/example.domain.com\/expiry<\/a><\/td><\/tr>
            url_target<\/code><\/td>String<\/em><\/td>Optional
            Possible values: _blank<\/code>, _self<\/code>, _parent<\/code>, _top<\/code> or custom iframe name.
            Find the result of applying the values in the HTML standard description (Browsing context names<\/a>)<\/td>            		Name of, or keyword for a browsing context where Customer should be returned according to HTML specification.
            Example:<\/strong> _parent<\/td><\/tr>
            req_token<\/code><\/td>Boolean<\/em><\/td>Optional
            default – false<\/td>            		Special attribute pointing for further tokenization
            If the card_token<\/code> is specified, req_token<\/code> will be ignored.
            For purchase and debit operations.
            Example:<\/strong> false<\/td><\/tr>
            card_token<\/code><\/td>Array of Strings<\/em><\/td>Optional
            String 64 characters<\/td>            		Credit card token value
            For purchase and debit operations.
            Example:<\/strong> f5d6a0ab6fcfb6487a39e2256e50fff3c95aaa97<\/td><\/tr>
            recurring_init<\/code><\/td>Boolean<\/em><\/td>Optional
            default – false<\/td>            		Initialization of the transaction with possible following recurring
            Only for purchase operation
            Example:<\/strong> true<\/td><\/tr>
            schedule_id<\/code><\/td>String<\/em><\/td>Optional
            It s available when recurring_init = true<\/td>            		Schedule ID for recurring payments
            Only for purchase operation
            Example:<\/strong> 57fddecf-17b9-4d38-9320-a670f0c29ec0<\/td><\/tr>
            vat_calc<\/code><\/td>Boolean<\/em><\/td>Conditional
            true or false
            default – false<\/td>            		Indicates the need of calculation for the VAT amount
            \u2022 ‘true’ – if VAT calculation needed
            \u2022 ‘false’ – if VAT should not be calculated for current payment.
            Only for purchase operation
            Example:<\/strong> false<\/td><\/tr>
            hash<\/code><\/td>String<\/em><\/td>Required<\/td>Special signature to validate your request to Payment Platform Addition in Signature section.
            Example:<\/strong> Must be SHA1 of MD5 encoded string (uppercased):<\/ins> order_number + order_amount + order_currency + order_description + password<\/td><\/tr>
            order<\/strong><\/td>Object<\/em><\/td>Required<\/td>Information about an order<\/td><\/tr>
            number<\/code><\/td>String<\/em><\/td>Required
            max: 255
            [a-z A-Z 0-9 -!”#$%&'()*+,.\/:;&@]<\/td>            		Order ID
            Example:<\/strong> order-1234<\/td><\/tr>
            amount<\/code><\/td>String<\/em><\/td>Required
            Greater then 0
            [0-9]
            max: 255<\/td>            		Format depends on currency.
            Send Integer type value for currencies with zero-exponent. Example:<\/strong> 1000
            Send Float type value for currencies with exponents 2, 3, 4.
            Format for 2-exponent currencies: XX.XX Example:<\/strong> 100.99
            Pay attention<\/strong> that currencies ‘UGX’, ‘JPY’, ‘KRW’, ‘CLP’ must be send in the format XX.XX, with the zeros after comma. Example:<\/strong> 100.00
            Format for 3-exponent currencies: XXX.XXX Example:<\/strong> 100.999.
            Format for 4-exponent currencies: XXX.XXXX Example:<\/strong> 100.9999
            For transfer operation:<\/strong>
            Send amount if you want to show default value in the amount field on the Checkout. The customers can change the value manually on the payment form.Send “-1” value if you want to show empty amount field on the Checkout so that the Customers could enter the value manually.<\/td><\/tr>
            currency<\/code><\/td>String<\/em><\/td>Required
            3 characters
            [A-Z]
            ISO 4217<\/a><\/td>            		Currency
            Example:<\/strong> USD<\/td><\/tr>
            description<\/code><\/td>String<\/em><\/td>Required
            min: 2 max: 1024
            [a-z A-Z 0-9 !”#$%&'()*+,.\/:;&@]<\/td>            		Product name
            Example:<\/strong> Very important gift – # 9<\/td><\/tr>
            customer<\/strong><\/td>Object<\/em><\/td>Conditional<\/td>Customer’s information. Send an object if a payment method needs<\/td><\/tr>
            name<\/code><\/td>String<\/em><\/td>Conditional
            min: 2 max: 32
            Latin basic
            [a-z A-Z]<\/td>            		Customer’s name
            Condition: If the parameter is NOT specified in the request, then it will be displayed on the Checkout page (if a payment method needs) – the “Cardholder” field
            Example:<\/strong> John Doe<\/td><\/tr>
            email<\/code><\/td>String<\/em><\/td>Conditional
            min: 2 max: 255
            email format<\/td>            		Customer’s email address
            Condition: If the parameter is NOT specified in the request, then it will be displayed on the Checkout page (if a payment method needs) – the “E-mail” field
            Example:<\/strong> example@mail.com<\/a><\/td><\/tr>
            birth_date<\/code><\/td>String<\/em><\/td>Conditional
            format: yyyy-mm-dd
            ISO 8601<\/a><\/td>            		Payer’s birth date
            Example:<\/strong> 1970-02-17<\/td><\/tr>
            billing_address<\/strong><\/td>Object<\/em><\/td>Conditional<\/td>Billing address information.
            Condition:<\/strong> If the object or some object’s parameters are NOT specified in the request, then it will be displayed on the Checkout page (if a payment method needs)<\/td><\/tr>
            country<\/code><\/td>String<\/em><\/td>Conditional 2 characters
            (alpha-2 code)
            ISO 3166-1<\/a><\/td>            		Billing country
            Example:<\/strong> US<\/td><\/tr>
            state<\/code><\/td>String<\/em><\/td>Optional
            min: 2 max: 32
            [a-z A-Z]
            It is 2-letters code for USA, Canada, Australia, Japan, India<\/td>            		Billing state address
            Example:<\/strong> CA<\/td><\/tr>
            city<\/code><\/td>String<\/em><\/td>Conditional
            min: 2 max: 40
            [a-z A-Z]<\/td>            		Billing city
            Example:<\/strong> Los Angeles<\/td><\/tr>
            district<\/code><\/td>String<\/em><\/td>Optional
            min: 2 max: 32
            [a-z A-Z 0-9 – space]<\/td>            		City district
            Example:<\/strong> Beverlywood<\/td><\/tr>
            address<\/code><\/td>String<\/em><\/td>Conditional
            min: 2 max: 32
            [a-z A-Z 0-9]<\/td>            		Billing address
            Example:<\/strong> Moor Building<\/td><\/tr>
            house_number<\/code><\/td>String<\/em><\/td>Optional
            min: 1 max: 9
            [a-z A-Z 0-9\/ – space]<\/td>            		House number
            Example:<\/strong> 17\/2<\/td><\/tr>
            zip<\/code><\/td>String<\/em><\/td>Conditional
            min: 2 max: 10
            [a-z A-Z 0-9]<\/td>            		Billing zip code
            Example:<\/strong> 123456, MK77<\/td><\/tr>
            phone<\/code><\/td>String<\/em><\/td>Conditional
            min: 1 max: 32
            [0-9 + () -]<\/td>            		Customer phone number
            Example:<\/strong> 347771112233<\/td><\/tr>
            payee<\/strong><\/td>Object<\/em><\/td>Conditional<\/td>Payee’s information.
            Specify additional information about Payee for transfer operation if it is required by payment provider.<\/td><\/tr>
            name<\/code><\/td>String<\/em><\/td>Required
            min: 2 max: 32
            Latin basic
            [a-z A-Z]<\/td>            		Customer’s name.
            Example:<\/strong> John Doe<\/td><\/tr>
            email<\/code><\/td>String<\/em><\/td>Conditional
            email format<\/td>            		Customer’s email address.
            Example:<\/strong> example@mail.com<\/a><\/td><\/tr>
            payee_billing_address<\/strong><\/td>Object<\/em><\/td>Conditional<\/td>Billing address information for Payee.<\/td><\/tr>
            country<\/code><\/td>String<\/em><\/td>Conditional 2 characters
            (alpha-2 code)
            ISO 3166-1<\/a><\/td>            		Billing country
            Example:<\/strong> US<\/td><\/tr>
            state<\/code><\/td>String<\/em><\/td>Optional
            min: 2 max: 32
            [a-z A-Z]
            It is 2-letters code for USA, Canada, Australia, Japan, India<\/td>            		Billing state address
            Example:<\/strong> CA<\/td><\/tr>
            city<\/code><\/td>String<\/em><\/td>Conditional
            min: 2 max: 40
            [a-z A-Z]<\/td>            		Billing city
            Example:<\/strong> Los Angeles<\/td><\/tr>
            district<\/code><\/td>String<\/em><\/td>Optional
            min: 2 max: 32
            [a-z A-Z 0-9 – space]<\/td>            		City district
            Example:<\/strong> Beverlywood<\/td><\/tr>
            address<\/code><\/td>String<\/em><\/td>Conditional
            min: 2 max: 32
            [a-z A-Z 0-9]<\/td>            		Billing address
            Example:<\/strong> Moor Building<\/td><\/tr>
            house_number<\/code><\/td>String<\/em><\/td>Optional
            min: 1 max: 9
            [a-z A-Z 0-9\/ – space]<\/td>            		House number
            Example:<\/strong> 17\/2<\/td><\/tr>
            zip<\/code><\/td>String<\/em><\/td>Conditional
            min: 2 max: 10
            [a-z A-Z 0-9]<\/td>            		Billing zip code
            Example:<\/strong> 123456, MK77<\/td><\/tr>
            phone<\/code><\/td>String<\/em><\/td>Conditional
            min: 1 max: 32
            [0-9 + () -]<\/td>            		Customer phone number
            Example:<\/strong> 347771112233<\/td><\/tr>
            parameters<\/strong><\/td>Object<\/em><\/td>Optional<\/td>Extra-parameters required for specific payment method
            Example:<\/strong>
            \"parameters\": { \"payment_method\": { \"param1\":\"val1\", \"param2\":\"val2\" } }<\/code><\/td><\/tr>
            custom_data<\/strong><\/td>Object<\/em><\/td>Optional<\/td>Custom data
            This block can contain arbitrary data, which will be returned in the callback.
            Example:<\/strong>
            \u201ccustom_data\u201d: {\u201cparam1\u201d:\u201dvalue1\u201d, \u201cparam2\u201d:\u201dvalue2\u201d, \u201cparam3\u201d:\u201dvalue3\u201d}<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n    
            \n            <\/h2>\n\n    
            \n        
            \n    
            Request parameter<\/h2>\n<\/div>\n
            • \n    
              <\/path><\/svg><\/path><\/svg><\/div>    \n        Authentication (OK)    <\/span>\n    <\/div>\n
              \n    
              curl –location -g –request POST ‘{{CHECKOUT_HOST}}\/api\/v1\/session’ <\/p>\n
              –header ‘Content-Type: application\/json’ <\/p>\n
              –data-raw ‘{<\/p>\n
                “merchant_key”: “xxxxx-xxxxx-xxxxx”,<\/p>\n
                “operation”: “purchase”,<\/p>\n
                “methods”: [<\/p>\n
                  “card”,<\/p>\n
                  “method1”<\/p>\n
                ],<\/p>\n
                “parameters”: {<\/p>\n
                  “card”: {<\/p>\n
                    “param1”: “val-1”,<\/p>\n
                    “param2”: “val-2”<\/p>\n
                  },<\/p>\n
                  “method1”: {<\/p>\n
                    “param1”: “val-3”,<\/p>\n
                    “param2”: “val-4”<\/p>\n
                  }<\/p>\n
                },<\/p>\n
                “session_expiry”: 60,<\/p>\n
                “order”: {<\/p>\n
                  “number”: “order-1234”,<\/p>\n
                  “amount”: “0.19”,<\/p>\n
                  “currency”: “USD”,<\/p>\n
                  “description”: “Important gift”<\/p>\n
                },<\/p>\n
                “cancel_url”: “https:\/\/example.domain.com\/cancel”,<\/p>\n
                “success_url”: “https:\/\/example.domain.com\/success”,<\/p>\n
                “expiry_url”: “https:\/\/example.domain.com\/expiry”,<\/p>\n
                “url_target”: “_blank”,<\/p>\n
                “customer”: {<\/p>\n
                  “name”: “John Doe”,<\/p>\n
                  “email”: “test@gmail.com”<\/p>\n
                },<\/p>\n
                “billing_address”: {<\/p>\n
                  “country”: “US”,<\/p>\n
                  “state”: “CA”,<\/p>\n
                  “city”: “Los Angeles”,<\/p>\n
                  “disctrict”: “Beverlywood”,<\/p>\n
                  “address”: “Moor Building 35274”,<\/p>\n
                  “house_number”: “17\/2”,<\/p>\n
                  “zip”: “123456”,<\/p>\n
                  “phone”: “347771112233”<\/p>\n
                },<\/p>\n
                “card_token”: [<\/p>\n
                  “f5d6a0ab6fcfb6487a39e2256e50fff3c95aaa97075ee5e539bb662fceff4dc1”<\/p>\n
                ],<\/p>\n
                “req_token”: true,<\/p>\n
                “recurring_init”: true,<\/p>\n
                “schedule_id”: “9d0f5cc4-f07b-11ec-abf4-0242ac120006”,<\/p>\n
                “hash”: “{{session_hash}}”<\/p>\n
              }<\/p>\n
              ‘<\/p>\n<\/div>\n<\/div><\/li>
            • \n    
              <\/path><\/svg><\/path><\/svg><\/div>    \n        Debit Operation (OK)    <\/span>\n    <\/div>\n
              \n    
              curl –location -g –request POST ‘{{CHECKOUT_HOST}}\/api\/v1\/session’ <\/p>\n
              –header ‘Content-Type: application\/json’ <\/p>\n
              –data-raw ‘{<\/p>\n
                “merchant_key”: “xxxxx-xxxxx-xxxxx”,<\/p>\n
                “operation”: “debit”,<\/p>\n
                “methods”: [<\/p>\n
                  “card”<\/p>\n
                ],<\/p>\n
                “parameters”: {<\/p>\n
                  “card”: {<\/p>\n
                    “param1”: “val-1”,<\/p>\n
                    “param2”: “val-2”<\/p>\n
                  },<\/p>\n
                  “session_expiry”: 60,<\/p>\n
                  “order”: {<\/p>\n
                    “number”: “order-1234”,<\/p>\n
                    “amount”: “0.19”,<\/p>\n
                    “currency”: “USD”,<\/p>\n
                    “description”: “Important gift”<\/p>\n
                  },<\/p>\n
                  “cancel_url”: “https:\/\/example.domain.com\/cancel”,<\/p>\n
                  “success_url”: “https:\/\/example.domain.com\/success”,<\/p>\n
                  “expiry_url”: “https:\/\/example.domain.com\/expiry”,<\/p>\n
                  “url_target”: “_blank”,<\/p>\n
                  “customer”: {<\/p>\n
                    “name”: “John Doe”,<\/p>\n
                    “email”: “test@gmail.com”<\/p>\n
                  },<\/p>\n
                  “billing_address”: {<\/p>\n
                    “country”: “US”,<\/p>\n
                    “state”: “CA”,<\/p>\n
                    “city”: “Los Angeles”,<\/p>\n
                    “disctrict”: “Beverlywood”,<\/p>\n
                    “address”: “Moor Building 35274”,<\/p>\n
                    “house_number”: “17\/2”,<\/p>\n
                    “zip”: “123456”,<\/p>\n
                    “phone”: “347771112233”<\/p>\n
                  },<\/p>\n
                  “card_token”: [<\/p>\n
                    “f5d6a0ab6fcfb6487a39e2256e50fff3c95aaa97075ee5e539bb662fceff4dc1”<\/p>\n
                  ],<\/p>\n
                  “req_token”: true,<\/p>\n
                  “hash”: “{{session_hash}}”<\/p>\n
                }<\/p>\n
              }<\/p>\n
              ‘<\/p>\n<\/div>\n<\/div><\/li>
            • \n    
              <\/path><\/svg><\/path><\/svg><\/div>    \n        Transfer Operation (OK)    <\/span>\n    <\/div>\n
              \n    
              curl –location -g –request POST ‘{{CHECKOUT_HOST}}\/api\/v1\/session’ <\/p>\n
              –header ‘Content-Type: application\/json’ <\/p>\n
              –data-raw ‘{  <\/p>\n
                 “merchant_key”:”xxxxx-xxxxx-xxxxx”,<\/p>\n
                 “operation”:”transfer”,<\/p>\n
                 “order”:{<\/p>\n
                    “number”:”order-1234″,<\/p>\n
                    “amount”: “100.55”,<\/p>\n
                    “currency”:”USD”,<\/p>\n
                    “description”:”Important gift”<\/p>\n
                 },<\/p>\n
                 “cancel_url”:”https:\/\/example.com\/cancel”,<\/p>\n
                 “success_url”:”https:\/\/example.com\/success”,<\/p>\n
                 “customer”:{<\/p>\n
                      “name”:”John Doe”,<\/p>\n
                      “email”:”success@gmail.com”<\/p>\n
                  },<\/p>\n
                  “payee”: {<\/p>\n
                      “name”:”John Doe”,<\/p>\n
                      “email”:”success@gmail.com”<\/p>\n
                      },<\/p>\n
                  “billing_address”:{<\/p>\n
                      “country”:”US”,<\/p>\n
                      “state”:”California”,<\/p>\n
                      “city”:”Los Angeles”,<\/p>\n
                      “address”:”Moor Building 35274 State ST Fremont. U.S.A”,<\/p>\n
                      “zip”:”94538″,<\/p>\n
                      “phone”:”0987654321″,<\/p>\n
                      “district”:”Brentwood”,<\/p>\n
                      “house_number”:”123″<\/p>\n
                  },<\/p>\n
                  “payee_billing_address”:{<\/p>\n
                      “country”:”US”,<\/p>\n
                      “state”:”New York”,<\/p>\n
                      “city”:”New York”,<\/p>\n
                      “address”:”Moor Building 35274 State ST Fremont. U.S.A”,<\/p>\n
                      “zip”:”94538″,<\/p>\n
                      “phone”:”0987654321″,<\/p>\n
                      “district”:”Brentwood”,<\/p>\n
                      “house_number”:”123″<\/p>\n
                  },<\/p>\n
                 “hash”:”{{session_hash}}”<\/p>\n
              }<\/p>\n
              ‘<\/p>\n<\/div>\n<\/div><\/li>
            • \n    
              <\/path><\/svg><\/path><\/svg><\/div>    \n        Example Response (OK)    <\/span>\n    <\/div>\n
              \n    
              {<\/p>\n
                “redirect_url”: “{{CHECKOUT_HOST}\/auth\/ZXlKMGVYQWlPaUpLVjFRaUxDSmhiR2NpT2lKU1V6STFOaUo5LmV5SnBZWFFpT2pFMU9UWXhPRFl6T0Rnc0ltcDBhU0k2SWpGbE5qTTNObVZoTFdRek1HUXRNVEZsWVMxaE16QXlMVEF5TkRKak1HRTRNekF4TWlJc0ltVjRjQ0k2TVRVNU5qRTRPVGs0T0gwLm9CMmVhdlRtTU5DMXFTajlDVFlqQ0dOMDlHdUs1NXRkQTVpWFR3d2F2cWR0cEpEU2NRWWFaT3Z5dmJSVjJUSFNUVlFlS0NUX3pRdFNycDlKS1M4X0pqUzRMclM5MnUyNXRfSHNGa1FUQ0VOdGtadHQtaGxONERYdVhkLTU5cEhKLUN1RXBqSmZ4UDZEQXhFaVAxWEpRZDlyQldNa1RQVDdGZm1ac0g4LTM5YnV6LTI3MWxKMndkekdvSGJYa0NKVnNTNFJldGxrbno2U3dGd3ZFMW5KNDhwYTBGMDNLWjBpNnhpRFVPR3p2U0ZKdGZfMndDTTdzTTdsemc1TlBmSDl0Q0RKQmZEaG1hUmJCRmR6RlZMZlJncG5tMzB3VWpTMGMxbmt6SkkxOGJTd2Z6Z0hfZFpnc1cyUFhCM2ZLdG9pWDJXeFRsQzlxR204QTRYVm9EQy1mOWxvRHlMd0F5eV9xY3JrWmNuQTJVSjk5Zl91c0cwODZKUlBTT0I4VHVRZndSTzUxSEN2bEU2TXdFYzVYRmtnYjBleEZRcXdpNGE4S2RlWV9HX3ZQam42bnpZODdtVzFINlpQMjJ0dzVzazYtUENMeHdvNXctUmFBWC1mYVVhcEVHTzFLZkVHbndaQWZBZVNyc3U4MV9XQUFJMlN5RUxGWi1IU1lXMUZLWFgybzNNeF93Ty1DS3FLTWZsUTV1cGc2eDAybzhsbFhoeGJlVmVIOWlkMHgzYldRWE9vWk5hWm1MeVpJMmJsT2dtVDV0cHR4NHNQNDNqT0NtYW1sdkxyUkZvQmxCNTJ4V0RUQTBZQnhBLW5meUxCRHRJN0dPaVRWQjJ5cWd1Z1lBdGRfbWFQN2x2YTJpbVJWaHhxT0R5SlRiZThxcDdhWkw4bkJvTHZocnZDOHlv”<\/p>\n
              }<\/p>\n<\/div>\n<\/div><\/li><\/ul>