Worldline Card Issuing in a Nutshell

A quick tour of Worldline Card Issuing

 

Worldline Card Issuing includes all the core features enabling to instantly issue cards and process payments

 

main offer

 

 

  • Issue any type of card : debit, credit, pre-paid whatever its form physical/virtual,

  • Authorize and process transaction efficiently thanks to a proven technology already processing more than 10 billions of transactions a year

  • Launch a new product on international schemes but also on local ones, Wordline Card Issuing being GLOCAL ! 

  • Embrace the wallet revolution by having the possibility to tokenize you card portfolio and make it compatible with mobile wallet providers

  • Manage disputes and initiate chargeback to a merchant in line with the schemes’ rules and regulation.

    Creating and managing your cards portfolio using Worldline Card Issuing will follow 4 main steps that can be easily done through our powerfull REST/json APIs.

     

    Enable "on this page" menu on doc section
    On

    Authentication doc

    Authentication

     

    Worldline APIs require authentication on all endpoints and methods.

    We currently support one Authentication scheme:

    • Bearer Token (OAuth2 - Client Credentials)

     

    Bearer Token

    Bearer tokens are temporary security credentials that can be used to authorize 'third parties' (bearers) access to the Worldline API.

    These tokens are created by calling the accesstoken endpoint.

    Once created the token field must be used in the HTTP Authorization header using the Bearer scheme.

     

    Example HTTPS request with a bearer token in Accept Transactions API

    GET /v1.0/acquiring/transaction/acquirers/{acquirerId}/transactions HTTPS/1.1
    
    Accept: application/json
    
    Authorization: Bearer fsdfdsfdsfdsfs9857958hjiIsInR5cCI6IkpXVCJ9

     

    Security Scheme Type

    HTTPS

    HTTP Authorization Schemebearer
    Header parameter nameauthorization

     

     

     

    Create Bearer Token - OAuth2 Client Credentials

    The Client Credentials grant type is used by clients to obtain an access token outside of the context of a user.

    The OAuth 2.0 client credentials grant flow permits an API (confidential client) to use its own credentials, instead of impersonating a user, to authenticate when calling another API.

     

    Steps to obtain an Access token

     

    Step 1: Construct a Basic Authentication header using the following values shared by Worldline team.

    Basic field

    Example

    consumerKeyjhfrjh881wtRxgregegegggeg
    consumerSecretwfrregergjbD6rNxregregerg

     

     

    Step 2: Construct a valid HTTP Basic Authentication header as follows in pseudo-code.

    const consumerKey = "jhfrjh881wtRxgregegegggeg";
    
    const consumerSecret = "wfrregergjbD6rNxregregerg";
    
    const authnValue = "Basic " + base64Encode(consumerKey + ":" + consumerSecret);
    
    request.setHeader("Authorization", authnValue);

     

    Security Scheme Type

    HTTPS

    HTTP Authorization Schemebasic
    Header parameter nameauthorization

     

     

     

    Step 3: Call the rest endpoint of Oauth2 client credentials to obtain the access token.

    POST oauth/client_credential/accesstoken?grant_type=client_credentials HTTPS/1.1
    Accept: application/json
    Authorization: Basic jfvwrjfbrkfbrkbrglenglengelgnegnejwvfwejhf==

     

    The call Response contains the Bearer Access token. Use this token to call the Actual resource.

     

    Example POST call response - field access_token

    {
        "refresh_token_expires_in": "0",
        "api_product_list": "[coffea]",
        "api_product_list_json": [
            "coffea"
        ],
        "organization_name": "$organization_name",
        "developer.email": "$Developermail",
        "token_type": "BearerToken",
        "issued_at": "1678146804722",
        "client_id": "jhfrjh881wtRxgregegegggeg",
        "access_token": "Knk9uvvoSALfzo3AGDADzGJ0Ayl1",
        "application_name": "4a319510-0793-4332-9627-452ae6a70c1d",
        "scope": "",
        "expires_in": "3599",
        "refresh_count": "0",
        "status": "approved"
    }
    Enable "on this page" menu on doc section
    On

    Accept Transactions API (test)

    Technical Description

     

    This API enables you to Accept transactions for your Merchant customers.

    Transactions are accepted via a host-to-host connection between the API user and Worldline FS API GateWay. The Worldline FS API GateWay is connected to the Worldline FS acceptance host, which in turn is connected to the Issuer network.

     

    Version note:
    This is a test version. Please be aware that these API interfaces are for evaluation. The API interfaces may be changed and improved.
    Initial production release is planned for Q2 2024 to accept Card Not Present transactions. The API roadmap for 2025 includes POS transaction acceptance via this API.
    The sandbox for this new API is not yet available causing the "Try out" feature to not work properly for this API.

     

    Latest open API spec below includes drop-down examples of requests (e.g. Purchase VISA Authorisation) and drop-down examples of successful "200" responses.

    Accept Transactions (test)

    Accept Transactions (test)

    This API enables you to accept Card Not Present (CNP) and POS transactions for your Merchant customers.

    Transactions are accepted via a host-to-host connection between the API user and Worldline FS API GateWay. The Worldline FS API GateWay is connected to the Worldline FS acceptance host, which in turn is connected to the Issuer network.

    Version note:
    This is a test version. Please be aware that these API interfaces are for evaluation. The API interfaces may be changed and improved.
    Initial production release is planned for Q2 2023 to accept Card Not Present transactions. The API roadmap for 2024 includes POS transaction acceptance via this API.

    Benefits for you!

    3rd party

    Third party access

     

    Allow your third party customers (Payment Facilitators and Merchants) direct access

    shopping

    Intuitive interaction

     

    Using acceptance actions (AUTH, PREAUTH, CAPTURE etc.)

    winkelwagenPOS

    Omni-channel

     

    Accept both Card Not Present and POS transaction requests

    Who can use the API?

    acq

    Acquirers

    psp

    PSPs

    merchant

    Merchants

    Acceptance actions

    AUTH

    CAPTURE

    AUTH_REVERSAL

    AUTH_REVERSAL_PARTIAL

    AUTH_INCREMENTAL

    AUTH_AND_CAPTURE

    PREAUTH

    Use Cases

    Purchase

    Refund

    Account Verification

    Recurring

    3D Secure v2

    Card-On-File

    Are you looking for more information?