Skip to content

PayCore.io v1.25 (November 24, 2020)

PayCore

By Dmytro Dziubenko, Chief Technology Officer

Cheery Greetings from PayCore.io!

Our team have launched some new features for products and upgraded card payments and integrations. So, check these notes to learn more about!

Highlights

In the Details

Card Gate Update

During the Host-to-Host payment connection, now you have an option to transfer data about the user browser and device to meet 3DS protocol requirements. You can add all necessary parameters as optional properties of the browser_info object at the Payment sale stage.

Request Example

{
"data": {
    "type": "sale-operation",
    "attributes": {
        "card_number": "5519283812030000",
        "card_holder": "Card Holder",
        "cvv": "123",
        "exp_month": "10",
        "exp_year": "35",
        "browser_info": {
            "browser_tz": "-60", 
            "browser_screen_width": "1920"
            }
        }
    }
}

Possible properties of the browser_info object
Property Type Description Example
browser_accept_header string HTTP accept headers as sent by the browser application/json, text/plain, */
browser_color_depth string Browser color depth 24
browser_ip string IP address returned by the browser 123.123.12.1
browser_java_enabled boolean Whether the browser can execute Java false
browser_language string Browser language (ISO code) en-US
browser_screen_height string Total height of the customer's screen in pixels 1200
browser_screen_width string Total width of the customer's screen in pixels 1920
browser_tz string Time difference between UTC time and the customer's browser local time, in minutes -120
browser_user_agent string Exact content of the HTTP user-agent header sent by the browser Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.135 Safari/537.36
device_channel string Device channel ID 02
window_height string Height of the customer's browser window in pixels 1200
window_width string Width of the customer's browser window in pixels 1920

Receipt Addon

We continue developing and upgrading our addons, so, among others, we have already got the first feedback about the Receipt Addon that allows us to move forward and find new solutions to improve the product.

The Receipt Addon is designed to generate the receipt files for the processed transactions, and now we expanded its functionality by adding new types of extensions for EDS Key. Therefore, the users can upload keys with Key-6.dat, *.pfx, *.pk8, *.zs2, or *.jks extensions and sign receipts with their own qualified electronic signature.

New and Updated Integrations

Provider Name New features
AlfaBank SOAP Flow (MOTO payments & quick reconciliation), REST Customer Data configuration update 
ComIn Bank H2H payment connection, Payouts, Account balances
Forward Bank 3DS 2.0 and failover for 3DS 1.0
SafeCharge 3DS 2.0 and 3DS 1.0 update

Besides, we added the {city} field to the dynamic descriptor for the Procard connection.

Card Holder Data Transfer

We should also highlight the added common standard scheme for transferring cardholder name parameter to the following connectors:

It is realised in the next sequence:

  1. If there is a saved card_holder parameter in the request or in the card vault, it is transferred unchanged.
  2. If no—we check the customer object and set the name.
  3. And in all other cases, transfer the parameter with the default value CARD HOLDER.

Bug Fixes

We also fixed some irritative bugs, and hopefully, you can mention boosting of the platform's productivity!

Stay tuned for the next updates!