Credit Account: as a customer, I want

Credit Account: As a customer, I want to

Change the credit limit

Update permanent credit limit

Close the credit card

Close card contract

(case of additional card)

or

Close contract

(if all cards of a contract must be closed)

Add a supplementary card to my card credit

Add an additional card to existing contract

Set up individual pricing for a specific customer

Create a consumer contract

The issuer can provide the fee models for a specific customer (account fee model, card fee model, membership fee model, account setup fee model)

See the customers payment free months

List contract fees for a contract

Change the minimum payment amount

Update account parameters

The issuer can provide the “amount due” model, the minimum amount and the % in case of partial payer
Enable "on this page" menu on doc section
On

Instant issuing

Instant issuing

As a customer, I want to issue card without plastic, to be used immediately

Create a consumer contract

Retrieve CVV2

Enable "on this page" menu on doc section
On

Product Features. As a Customer,

Product Features. As a Customer, I want to

Change my embossing name

Update card contract

The change applies then for all next cards

Replace Card

The change applies only for the next card

Activate my card

Activate a card

Change my geo-blockings

Create authorization restriction override

Update authorization restriction override

Change my cash withdraw limit

Create VL override

Update VL override

Change my POS limit

Create VL override

Update VL override

Change my internet usage limit

Create VL override

Update VL override

Deliver card using express priority

Create a consumer contract

The issuer can provide the sending mode if a physical card (card order) is requested. Default sending mode is retrieved from configuration.

Change the delivery method of my card

Initial card creation:

Create a consumer contract

The issuer can override the delivery method for the first card. OR The issuer provides the distribution model reference for all next cards

For the next cards:

Update card contract

The issuer provides the distribution model reference for all next cards

Replace card

The issuer can override the delivery type for the current card and the delivery address

My card delivered to a temporary address

Replace card

The issuer can provide an address for the card replacement

Card renewal with the same card number (card not working)

Replace card

The issuer provides the replacement reason corresponding a card not working

I want to turn internet usage on/off

Create authorization restriction override

Update authorization restriction override

Turn contactless on / Off

Create authorization restriction override

Update authorization restriction override

Choose a PIN for a new Card

Set a PIN before card production

Get PIN digitally

Display PIN

Receive PIN reminder/view PIN

Request a PIN reminder

Display PIN

Change PIN delivery method

Initial card creation:

Create a consumer contract

The issuer can override the delivery method for the first PIN. OR The issuer provides the distribution model reference for all next PINs

For the next cards:

Update card contract

The issuer provides the distribution model reference for all next cards

Replace card

The issuer can override the delivery type for the current card and the delivery address

Block by card, as I have lost it

Block a card

Unblock my card, as I reported it lost but now I have found it

Unblock card

I want to terminate my card

Deactivate card

New validity period (card renewal with same card number)

Replace card

The expiry date can be overridden if this is allowed in the configuration

Change my spending limit

Create VL override

Update VL override

Block all gambling/online gambling with my card

Create authorization restriction override

Update authorization restriction override

Change all addresses for my family

Update addresses of all contract members

Transfer funds from my Credit card account to Bank Account

Initiate outgoing credit transfer

Enable "on this page" menu on doc section
On

Back Office team/Card Boarding Department

Back Office team/Card Boarding Department: As a customer, i want to

Order debit card

Create a consumer contract

The issuer should provide the corresponding debit product reference

Issue card without plastic, to be used immediately

Create a consumer contract

The issuer should provide the corresponding product reference

Add new cards to existing accounts

Add card to existing contract

Enable "on this page" menu on doc section
On

Use Case Mapping

Use Case Mapping

Back Office team/Card Boarding Department

As a Customer, I want to

Product Features.

As a Customer, I want to

Instant issuing

As a Customer, I want to

Credit Account

As a Customer, I want to

Transactions

As a Customer, I want to

Dispute

As a Customer, I want to

Token management

As a Customer, I want to

Corporate hierarchy

As a Bank employee, I want to

Enable "on this page" menu on doc section
On

Buy Now Pay Later

Buy Now Pay Later

Buy now, pay later is a payment method that allows consumers to buy a product immediately and pay later. This payment method is gaining popularity around the world, especially among younger consumers.

Buy Now Pay Later works like this: Consumers make purchases online or in-store, then select the Buy Now Pay Later payment method. The consumer can then select a later payment date that is convenient to him. Depending on the terms of the contract, fees or interest may apply to this payment method.

Buy now, pay later offers consumers several benefits, including the ability to defer payments to a later date, which can help during temporary financial hardship. Additionally, consumers can better manage their budgets by spreading payments over multiple months.

Pay later usage are rising

globe

Global sales using Buy Now Pay Later reach €93B in 2020

growth

Will exceed €181B in 2022, and would reach 10X this volume in 2025

profile

75% of Buy Now Pay Later users are aged 18-36

How does it work ?

Instalment via push notification
phone and card

In the moment of card purchase, the banking app receives a push notification

phone

User can tap on it, see the details and select an instalment plan

phone

Split of transactions confirmed in banking app

Card control

Card control

Card Control enables the cardholder to manage his card in real-time. Cards can be managed via the banking app or online banking through our APIs

The cardholder knows best his habits and preferences for card usage. Card Control allows him/her to customize a card in different aspects. Some examples: set card limits on different channels – in-store/online/contactless payments, cash withdrawals at ATM. As well it is possible to block chosen payment channels or certain merchant categories (e.g., casinos, liquor store, etc.). Geographical reach can also be controlled: countries can be blocked or enabled for card payments. All the mentioned features can be set for a specific period of time. Altogether, a variety of features and its combination provide a detailed customization.

Thanks to a comprehensive customization, Card Control becomes a first step towards risk mitigation. Through spending limit management, country and merchant category blocks, spend notifications, etc. the cardholder gets alert about fraudulent activities and can prevent it. Next to this, extensive card self-management options lead to fewer disputes and a lower number of calls to the customer care center.

iphone

The cardholder loses a physical card. He/she opens the banking app and blocks the cards easily.

card

A new card is issued instantly. The cardholder customizes it by setting spending limits, blocking some merchants and activating notifications?

globe

The cardholder is getting ready for a trip. Before travelling, he/she activates payments by his/her card in specifi countries.

How it works ?

 

Card Control allows the cardholder to personalize his card overriding the issuer specific standard settings. The customization is achieved by updating and overriding cards authorization restrictions and velocity limits.

Each authorization restriction override is based on an existing authorization restriction. First step is to retrieve the authorizationRestrictionReference through the list of existing authorization restriction by calling the API List of authorization restriction for account. Second step is to modify the authorization restriction using the API Create authorization restriction override. The override created could be then updated using the appropriate API. 

Similar process applies to velocity limits. A default velocity limit could be overwritten by Velocity limit overrides API that allows to modify number and amount of authorizations allowed for a specific time period. The override created could be then updated and deleted using the appropriate API.

Merchant management (old version)

Technical Description

 

The WL FS merchant contract API enables retrieval and updating at site & terminal level. Access to contract data is restricted to your acquirer and own merchant contract identifiers. For third parties, contract updating is limited depending on the generic user role (e.g. PSP, PayFac, Merchant) limitations agreed with the acquiring bank.

Version note:
Please be aware that these API interfaces may be changed and improved (e.g. addition of fields).

The "Try out" feature does not work at this time because the sandbox is being improved to support new functionality.

View Documentation

Accounts

Accounts (Features For All Card Types)

Accounts are used to process operations, manage a balance in a dedicated currency, control the credit risk, perform transaction charging, calculate interest (credit or debit), generate an invoice (statement), process payments.

Three types of account working modes are being supported; Pay Later, Pay Now, Pay Before.

  • Pay Later account working mode is used to implement classical credit card products like charge cards or revolving credit. Pay later accounts are settled by a cyclic closure process and typically produce an invoice (statement) with an amount due which can represent the full or partial statement balance. Credit or debit interest algorithms may apply.
  • Pay Now account working mode is used for all types of debit cards. Such accounts are typically settled in short frequencies (e. g. daily) and produce debit orders, immediately forwarded to customers’ current accounts. Interest calculation never applies.
  • Pay Before account working mode is used for the wide range of prepaid card products. The balance is always positive.

The below diagram presents different use cases covered by the API in the account domain.

account diagram

Enable "on this page" menu on doc section
On

ob-p-ideal-notification

Notification API

for iDEAL 2.0

API Reference

The notification APIs described in this chapter needs to be implemented on the Initiating Party side, if the Initiating Party decides to use them. The Open Banking Service will post notifications to these endpoints. For the iDEAL product the post status notification is part of the product, a value-added service is not required (because the notification is part of the iDEAL scheme and the Open Banking Service doesn't have to-do additional polling).

POST Status

Endpoint: POST /status

This API will notify the initiating party about the status of the payment. More details about the fields can be found in the API reference.

Data model

Legend

  • Orange fields: mandatory for an iDEAL payment
  • Purple fields: conditionally mandatory for an IDEAL payment
Request (click to enlarge)Response
Post status iDEAL requestpost status iDEAL response

Example: Notification for Standard iDEAL payment

Request (Signature-related fields "Digest" and "Signature" are conditionally present):

Address: https://checkout.company.com/transaction/webhook/91FA6EEC30844FAAB5/v3/notification/status
  HttpMethod: POST
  Headers: {Authorization=Bearer 123456789, X-Request-ID=c1452392-6c3f-4365-93f8-40558f61ac36, MessageCreateDateTime=2023-03-15T11:51:24.185+01:00, Digest=SHA-256=0hq1mKzxB1yyc6+hut2bEX7ps+nWyWb2pgQb6AhfhfM=, Signature=keyId="3EBEF6033C00730D9C6DA05165A3CAA1F31036FB",algorithm="rsa-sha256",headers="messagecreatedatetime x-request-id digest",signature="uYgovoK+ibAE7+MzJEKrApDUAgWfUv7RQK22zAxWHCdKCuG4d0HgqpDSqcGlKmP2IMFsC787zDU3oqKeeIIVXR72uZBiOnm0/84UL9e7LVDHDLQsRbfDnmvgX/4xQvdwROmyqh8kkcXTf/48zY0wo2n9iDspCbgTn1DEqAqtAlwunIpea8eYA3FQc+pV2px77wVP7l+9mTxexzLSmum61wWbqE4ESJn0K37gXY54229ZtCnNSlu9rsvjQ5xmDf1e6MvMLBOblXHIReN2t8IH85VGK7mpi8T7JeKb8rIG8qDbQ5TD3BmIS1+RspI95FldLCKLH91/KNrxsgPsrC2QgQ==", Content-Type=application/json}
  Payload: {
  "PaymentProductUsed" : "IDEAL",
  "CommonPaymentData" : {
    "GuaranteedAmount" : "10.00",
    "PaymentStatus" : "SettlementCompleted",
    "PaymentId" : "19928",
    "AspspPaymentId" : "0001070883053837",
    "AspspId" : "10002",
    "DebtorInformation" : {
      "Name" : "Edsger Wybe Dijkstra - Callback",
      "Agent" : "ABNANL2AXXX",
      "Account" : {
        "SchemeName" : "IBAN",
        "Identification" : "NL44RABO0123456789",
        "Currency" : "EUR"
      },
  "UseWaitingScreen" : false
}

Response:

ResponseCode: 204

Example: Notification for iDEAL Payment with Fast Checkout

Request (Signature-related fields "Digest" and "Signature" are conditionally present):

Address: https://checkout.company.com/transaction/webhook/91FA6EEC30844FAAB5/v3/notification/status
  HttpMethod: POST
  Content-Type: application/json
  Headers: {Authorization=Bearer 123456789, X-Request-ID=c1452392-6c3f-4365-93f8-40558f61ac36, MessageCreateDateTime=2023-03-15T11:51:24.185+01:00, Digest=SHA-256=0hq1mKzxB1yyc6+hut2bEX7ps+nWyWb2pgQb6AhfhfM=, Signature=keyId="3EBEF6033C00730D9C6DA05165A3CAA1F31036FB",algorithm="rsa-sha256",headers="messagecreatedatetime x-request-id digest",signature="uYgovoK+ibAE7+MzJEKrApDUAgWfUv7RQK22zAxWHCdKCuG4d0HgqpDSqcGlKmP2IMFsC787zDU3oqKeeIIVXR72uZBiOnm0/84UL9e7LVDHDLQsRbfDnmvgX/4xQvdwROmyqh8kkcXTf/48zY0wo2n9iDspCbgTn1DEqAqtAlwunIpea8eYA3FQc+pV2px77wVP7l+9mTxexzLSmum61wWbqE4ESJn0K37gXY54229ZtCnNSlu9rsvjQ5xmDf1e6MvMLBOblXHIReN2t8IH85VGK7mpi8T7JeKb8rIG8qDbQ5TD3BmIS1+RspI95FldLCKLH91/KNrxsgPsrC2QgQ==", Content-Type=application/json}
  Payload: {
  "PaymentProductUsed" : "IDEAL",
  "CommonPaymentData" : {
    "GuaranteedAmount" : "10.00",
    "PaymentStatus" : "SettlementCompleted",
    "PaymentId" : "19928",
    "AspspPaymentId" : "0001070883053837",
    "AspspId" : "RABONL2UXXX",
    "DebtorInformation" : {
      "Name" : "Edsger Wybe Dijkstra - Callback",
      "Agent" : "ABNANL2AXXX",
      "Account" : {
        "SchemeName" : "IBAN",
        "Identification" : "NL44RABO0123456789",
        "Currency" : "EUR"
      },
      "ContactDetails" : {
        "FirstName" : "Edsger",
        "LastName" : "Dijkstra",
        "PhoneNumber" : "+31612345678",
        "Email" : "edsger@domain.nl"
      },
    "ShippingAddress" : {
        "FirstName" : "Edsger",
        "LastName" : "Dijkstra",
        "PostCode" : "52066",
        "Country" : "NL"
        },
    "BillingAddress" : {
        "FirstName" : "Edsger",
        "LastName" : "Dijkstra",
        "PostCode" : "52066",
        "Country" : "NL"
        }     
    }
  },
  "UseWaitingScreen" : false
}

Response:

ResponseCode: 204

POST Debtor token

Endpoint: POST /debtorToken

This API will provide a debtor token update to the Initiating party. More details about the fields can be found in the API reference.

Data model

Legend

  • Orange fields: mandatory for an iDEAL payment
  • Purple fields: conditionally mandatory for an IDEAL payment
RequestResponse
post debtorToken iDEAL requestpost debtorToken iDEAL response

Example: Debtor Token Notification for Standard iDEAL payment

Request (Signature-related fields "Digest" and "Signature" are conditionally present):

Address: https://checkout.company.com/transaction/webhook/91FA6EEC30844FAAB5/v3/notification/status
  HttpMethod: POST
  Content-Type: application/json
  Headers: {Authorization=Bearer 123456789, X-Request-ID=c1452392-6c3f-4365-93f8-40558f61ac36, MessageCreateDateTime=2023-03-15T11:51:24.185+01:00, Digest=SHA-256=0hq1mKzxB1yyc6+hut2bEX7ps+nWyWb2pgQb6AhfhfM=, Signature=keyId="3EBEF6033C00730D9C6DA05165A3CAA1F31036FB",algorithm="rsa-sha256",headers="messagecreatedatetime x-request-id digest",signature="uYgovoK+ibAE7+MzJEKrApDUAgWfUv7RQK22zAxWHCdKCuG4d0HgqpDSqcGlKmP2IMFsC787zDU3oqKeeIIVXR72uZBiOnm0/84UL9e7LVDHDLQsRbfDnmvgX/4xQvdwROmyqh8kkcXTf/48zY0wo2n9iDspCbgTn1DEqAqtAlwunIpea8eYA3FQc+pV2px77wVP7l+9mTxexzLSmum61wWbqE4ESJn0K37gXY54229ZtCnNSlu9rsvjQ5xmDf1e6MvMLBOblXHIReN2t8IH85VGK7mpi8T7JeKb8rIG8qDbQ5TD3BmIS1+RspI95FldLCKLH91/KNrxsgPsrC2QgQ==", Content-Type=application/json}
  Payload: {
  "PsuId": "TestOSZ",
  "PaymentId": "12345",
  "DebtorToken": "absjrfergd"
 }

Response:

ResponseCode: 204
Enable "on this page" menu on doc section
On
Subscribe to