Additional configurations that may be useful in different cases.

POST request customization

In the post request to pl/create-session-token you can add certain optional fields that allow a certain degree of customization in the payment session that the client receives.

Dynamic successful and cancelled payment URLs

A structure with rules for merchants is implemented. This structure is optional, it is part of each merchant in the collection within the database and consists for now of 2 rules oriented to return URLs, but with the possibility of incorporating additional ones in the future:

General validation of return URLs:.

• It applies to all return URLs, whether by default or passed by parameter.
• The basic structure of a URL (consisting of an http or https protocol, hostname, optional port and path) is validated by means of a regular expression.

Expected parameters:

• payment_completed_url: URL to be taken for redirection of a successful payment.
• payment_cancellation_url: URL to be taken for the redirection of a cancelled payment.
• concat: If the path contemplates the use of parameters, it is appropriate to send this parameter to indicate the character that should be used to concatenate something to that URL.

StartSession URL:pl/create-session-token: call.

The pl/create-session-token call does not undergo any change in the response structure, only that when the call is made the mentioned parameters can be incorporated.

Headers:

{
    "x-api-key": "{MERCHANT_API_TOKEN}"
}

Body:

{
    "merchant_code": "{MERCHANT_CODE}",
    "merchant_order_id": "{ORDER_ID}",
    "order_amount": 500,
    "customer_email": "[email protected]",
    "payment_completed_url": "{URL_SUCCESS}",
    "payment_cancellation_url": "{URL_CANCEL}",
    "concat":"{“&”}",
    "metadata":[{
        "name": "Title",
        "value": "subtitle",
        "show": true
    }]
}

Rules