# Trending

What are Integration Dashboards?

Integration Dashboards offer an overview of your API requests and responses, helping you gauge the health of your integrations and identify areas for improvement to boost successful transactions.

In a user-friendly interface, you can easily track both successful and failed API requests, gaining insights through detailed logs. The error overview feature allows you to identify and resolve issues quickly, optimizing your integration experience with us.

Benefits of using Integration Dashboards

• Boost transaction success: analyze your API requests and errors to identify and resolve issues impacting your transaction success rate.
• Real-time monitoring: keep track of your integration performance and observe the immediate effects of updates or changes.
• Comprehensive error overview: quickly pinpoint areas for improvement, facilitating swift troubleshooting and error resolution.

Explore the available features

Dashboard Page:

• Summarize your API requests with visual graphs showing both successful and failed attempts.
• Use filters to focus on the data most relevant to you.

API Logs Page:

• Access detailed logs for each API call.
• Review specific information, including headers, metadata, requests, and responses.

Error Overview Page:

• View a table of aggregated errors for each API endpoint.
• Identify error causes quickly and take action to resolve them.

Integration Dashboards empower you with insights and tools to optimize your integration. Ready to enhance your API performance and boost transaction rates? Log in to the Configuration Center and discover the capabilities of Integration Dashboards!

What is payment product ordering?

Payment product ordering allows you to customize the order in which the payment products are displayed to your consumers in a manner that aligns with consumer preferences based on the country of the transaction.

In certain countries, specific regulations require that payment products be displayed in a particular order, as in the Finland and Sweden regulations. For these use cases, payment product ordering is not only a powerful commercial advantage but also a compliance necessity.

Key benefits:

Our top priority is to help you boost your revenue. We believe that customizing the order of payment products can significantly assist in this effort and offers the following benefits:

• Enhanced consumer experience: showcase familiar and locally preferred payment options to your consumers.
• Increased conversion rates: cater to local tastes and reduce the chance of payment abandonment.
• Simple customization: easily modify the order of payment products to keep up with changing regional trends and preferences.

How to make use of payment product ordering?

1. Log in to the Configuration Center and select the merchant ID at the top for which you want to customize the order.
2. Go to "Merchant Settings," click on "Payment Products," and then choose "Payment Product Ordering."
3. Select the country for which you want to customize the order using the drop-down field.
4. Simply drag and drop the payment products into your preferred order.
5. When you're done, click "Save Changes." The changes will take effect immediately.

You have the flexibility to add or delete customized orders anytime. Go to the table below, click "Actions" and then "Edit" to make adjustments.

Integration process

If you're using the MyCheckout hosted payment pages for selecting payment products, your customers will automatically see the customized order you've set up in the Configuration Center.

If you have your own custom payment product selection page, you can use the GET paymentProduct(s) API call to access the recommended order. The displayOrder property in the API response shows our suggested order for displaying the payment products, starting with 0, followed by 1, 2, and so on.

For more editing options, feel free to explore our comprehensive guide on payment product ordering.

What is AI-assisted search?

To improve access to information and the documentation experience on our developer portal, we've integrated AI into our search function. This enhanced AI-assisted search goes beyond basic keyword matching. It understands the context of your questions, providing informative and detailed responses. With this new functionality, finding the answers you need is faster and more intuitive than ever.

Enhancing your integration experience

Understanding that our users have varied professional roles, from product managers to developers, we've launched the AI-Assisted Search. This feature is designed to meet the unique needs of each user by simplifying the search process and delivering relevant answers quickly. It helps you find the information you need faster, facilitating your integration with our services. This reduces your need to contact us directly and significantly speeds up the time it takes for you to go live.

Experience it yourself

At the top of the developer portal, you'll find a search bar labeled "Search AI-Powered." Just type in your question and let the AI provide you with a detailed answer, along with links to additional resource pages for further reading. Below the AI's detailed response, you'll find regular search results if you're simply searching for a specific documentation page.

Not sure where to begin? We've provided a set of predefined questions you can ask the AI to explore its capabilities and see how it can assist you.

We value your feedback

After using the AI-assisted search, we encourage you to share your thoughts through the feedback tool found at the bottom of the AI’s response. This tool allows you to give a thumbs up or thumbs down, and you can also provide more detailed comments in the text box. Your feedback is vital for us to keep improving the documentation and ensure AI delivers the most helpful answers possible.

How does native checkout impact consumer experience?

Redirecting consumers to external pages for payment often leads to increased load times and a higher likelihood of timeouts, especially on mobile devices. This can result in higher cart abandonment rates. To counter this, creating a native checkout experience within your mobile app or web browser is essential. It keeps the consumer engaged on your platform.

Key benefits:

• Entire payment process occurs within the app: it eliminates the need for any redirects
• Boosted conversion rates: a native checkout experience helps retain consumers on your mobile application
• Enhanced user journey: native interfaces are designed to be responsive, adapting to different screen sizes and device types

In addition to our Android and iOS SDKs, we now introduce our Flutter SDK. This cross-platform solution is designed to facilitate the creation of native checkout experiences, offering a unified and efficient approach for both Android and iOS platforms. 

Why choose Connect Flutter SDK?

Flutter, developed by Google, stands out as a versatile cross-platform SDK, enabling the creation of native-like mobile applications for both Android and iOS from a single codebase. This efficiency is a significant advantage in today's fast-paced development environment. 

Our Flutter SDK allows you to communicate with the Client API of Connect, offering the following advantages:

• optimized mobile checkout experience
• convenient Dart wrappers for API responses
• user-friendly formatting of payment data
• validation of input
• encryption of payment details

Main payment steps

1. Initialize the Flutter SDK

Start by initializing the Flutter SDK for the payment process. This involves inputting essential information such as session and customer identifiers, connection endpoints, and specific payment details like currency and the total amount.

1. Retrieve payment items and accounts on file

Use the Client API to fetch payment items and accounts on file that are applicable for this payment. This data is crucial for your application to construct the payment product selection screen, where consumers choose their preferred payment method.

1. Obtain payment product details

Next, retrieve details about the payment product fields from the Client API. This information enables your app to create a detailed payment product details screen for the consumer.

1. Consumer information input

At this stage, the consumer is required to provide necessary information based on their selected payment product or account on file.

1. Encrypt payment information

All the payment information provided by the consumer can be securely encrypted using the Client API.

1. Send encrypted data to the e-commerce server

Once the payment information is encrypted, your app will send this data to your server. The server forwards this information to our Server API.

1. Handle the Server API response

Use the response received from the Server API to direct the consumer to the next phase of the payment process. This could range from displaying a simple "payment successful" or "payment failed" message to redirecting the consumer to a third-party site to complete the payment.

For more in-depth instructions on using the Flutter SDK for payment integration, it's recommended to visit the Flutter SDK documentation page.

Frequently asked questions

What can I do with the Flutter SDK of Connect?

• Retrieve payment products based on customer location and currency.
• Access customer accounts and tokens using the customer ID
• Obtain detailed information about payment products, including names, logos, and required customer data for successful payment processing
• Encrypt payment information for secure transmission to your e-commerce server and our Server API
• Use services like "Convert Amount" for currency conversion and "Get IIN Details" for card information (scheme, issuing country, etc.)

For more details, refer to our Client API reference.

What are the limitations of the Flutter SDK?

The Flutter SDK does not support direct payment creation. This action must be performed by your server, not through the consumer's device, as per the guidelines for all our Client SDKs.

Where can I find detailed information about the Flutter SDK?

For comprehensive information on the Flutter SDK, please visit our Flutter SDK documentation.

Where can I find the GitHub repository for the Flutter SDK?

The GitHub repository for our Flutter SDK is available at Connect Flutter Client SDK.

Benefits for you and your consumers

The regulation is oriented toward having an improved user experience by reducing the number of complaints and chargebacks related to consumers who:

• didn't intend to enroll in a subscription
• didn't recognize the transaction associated with this subscription
• have trouble canceling their subscription

What are the regulations?

Free/low-cost trial (negative option billing)

This subscription model suggests that you offer a free or low-cost trial period of a digital good (streaming service, club membership, website access, or software license) and then automatically enroll the consumer into a subscription plan at the end of the trial period (also called "negative option billing").

You're required to inform the consumer about the upcoming start of the subscription plan at least 3 days but no more than 7 days before the trial period concludes or whenever there are changes in the terms and conditions. This notification must include the following information:

• basic terms of the subscription
• instructions on subscription cancellation

The notification can be sent by email or any other electronic method.

Subscription/recurring payments

In addition to the requirements for a free/low-cost trial, you must adhere to regulations related to the information shown during the payment process and inform the consumer.

Payment

At the point of payment, you must clearly disclose the basic terms of the subscription, which contain:

• billing price billing frequency (for example, "You will be billed EUR 9.95 per month until you cancel the subscription.")

In case of a negative billing option, also disclose the following:

• terms of the free/low-cost trial, including any initial charges
• length of the trial period
• price and frequency of the subsequent subscription (for example: "You will be billed EUR 2.99 today for a 30-day trial. Once the trial ends, you will be billed EUR 9.95 each month until you cancel.")
• capture the consumer's affirmative acceptance of such terms

The point of payment includes the screen where the consumer enters their card details and any screens that show a summary of the order before it's submitted for authorization to the consumer.

Confirmation to the consumer at the time of enrollment

You must send a confirmation by email or any other electronic method at the time of enrollment in a subscription/recurring billing plan that provides the following:

• terms of the subscription, including the trial period terms when applicable
• clear instructions on how to cancel the subscription

Confirmation to consumer after every billing

You must send a receipt by email or any other electronic method after every billing, including clear instructions for canceling the subscription.

Please note that Mastercard standards prohibit merchants from submitting subsequent authorization requests on the same primary account number (PAN) when the original authorization response included specific response codes. Refer to AN 1704—Multiple Authorization Requests for Card-Not-Present Transactions.

Cancellation methods for consumers

You must provide your consumers with an online or electronic cancellation method, making it easy for them to cancel their subscriptions.

Notification for billing plans less frequently than every six months

For any subscription/recurring payment plan that bills a consumer less frequently than every 6 months (180 days), you must send a notification no less than 3 days and no more than 7 days before the billing date that includes the terms of the subscription and instructions about how your consumer may cancel the subscription.

What do you have to do?

If you create your own checkout page, you must implement these regulations yourself. If you use our MyCheckout hosted payment pages, you'll simply need to send the relevant data to us, as we've already handled the payment-related requirements. Read more information in our subscription details guide.

When was the regulation implemented? 

The requirements became effective as of March 22, 2022 (except the requirement to disclose at the point of payment, which came into effect on September 22, 2022).

Should the same be implemented for transactions of other card schemes?

Although you're not obliged to do the same for other card schemes, disclosing any information related to subscriptions is recommended.

Where can I read the official regulation?

You can find more information in the official Mastercard documentation.

What is two-factor authentication?

Two-factor authentication is a security process in which users provide two different authentication factors to verify their identity. Typically, this involves something the user knows (like a password) and something the user has (like a security token). 

Why is it important to have two-factor authentication enabled? 

The primary goal of two-factor authentication is to fortify security by introducing an additional layer of protection against potential attackers. Even if someone obtains a user's data for logging in, they would still need the second form of authentication to gain access. This additional layer of defense makes it significantly more challenging to compromise accounts.

For which application was two-factor-authentication enabled?

• Configuration Center - used for managing integration on your end (available in sandbox, pre-production, and production environments)

What authentication apps should be used?

To initiate the two-factor authentication setup process, start by downloading an authenticator app on your mobile device. Two examples of the popular apps are:

• Google Authenticator (Google Play Store or Apple App Store)
• Microsoft Authenticator (Google Play Store or Apple App Store)

What should be done from your side?

1. Download one of the authenticator apps to your mobile device.
2. Set up the two-factor authentication in the Configuration Center using our instructions.
3. Log in to the Configuration Center, providing the one-time password (OTP) from the authenticator app.

Additional information

• In the future, you'll need to provide the one-time password next to your username and password to log in
• For each environment (sandbox, pre-production, and production), you'll need to set up two-factor authentication separately
• The one-time password is specific to the device and can't be used with another one
• You can always reset the two-factor authentication by following our guidelines

Using the key instead of the QR code to set up two-factor authentication

If you can't scan the QR code with your mobile device's camera, setting up two-factor authentication using the authenticator app is still possible.

1. Log in to the Configuration Center (sandbox, pre-production, and production environment)
2. You'll see the page to set up the two-factor authentication. Click on the "unable to scan code?" link.
3. You'll be shown a key that you must add to the authenticator app (copy and paste the key into the app). 
4. Provide the name for your one-time password (we suggest using "Worldline Connect.")
5. In your authenticator app, you'll see the "Worldline Connect" and the one-time password (OTP): a six-digit code that constantly refreshes. Enter this one-time password and press submit.

Is it possible to reset the two-factor authentication?

• resetting two-factor authentication yourself
• resetting two-factor authentication by the account admin
• resetting two-factor authentication by our team

Support 

For the frequently asked questions regarding the two-factor authentication, please check the FAQ section of our guide. If you need additional assistance, get in touch with our support team: merchantservices@worldline.com

Key benefits at a glance

• Hassle-free integration

Take the development complexity away and focus on your go-to-market strategy while everything else has been taken care of.

• Boundless potential for your online business

You can choose from various countries, payment methods and currencies to enable new markets as you grow.

• Constantly evolving solution

New features and payment methods are rolled out to expand our offering. Keep an eye on our documentation to always be up-to-date. 

• Access to unique services 

Choose from best-in-class fraud solutions like Microsoft Dynamics 365 Fraud Protection, access valuable information for comparing your performance to the industry competitors, receive continuous hands-on support from our industry experts, and more.

How we can help you

We'll support your end-to-end integration via Magento 2 plugin to Worldline Global Collect. You can count on our expertise to find the most fitting setup for your business, benefit from our global and local payment solutions, and reach emerging markets along the way. 

Different processing flows

There are several processing flows supported within the plugin's capabilities. You can choose the one fitting your business better: 

• Create your own checkout page: use the server-to-server API calls to create transactions managed directly from the platform to our payment engine
• Full redirect to MyCheckout hosted payment pages: your consumers select the payment product and pay with this on payment pages hosted by us
• Finalize payment on MyCheckout hosted payment pages: your consumers select the payment product on your checkout page and get redirected to finalize the transaction on a payment page hosted by us

Sandbox testing and demo

You can experience the plugin's features and benefits firsthand with our sandbox environment. It provides a risk-free space where you can explore all the functionalities and make sure our plugin aligns perfectly with your requirements. Dive into the sandbox, experiment with its various elements, and gain the confidence you need for a successful implementation. If you prefer not to conduct sandbox testing on your own, save effort and request a demo video walkthrough by messaging us. 

Getting started with Magento 2

1. Set Worldline account

To start using Magento 2 plugin, you need to have a Worldline Global Collect account. Contact us so we can take care of setting up an account for you. 

1. Install our plugin

Download the plugin itself from our GitHub and follow the comprehensive guide on installing Magento 2.

1. Take care of the configuration

All the necessary configuration tweaks are described in our easy-to-follow instructions, together with additional settings.

Support 

If you face any technical issues, you have two options for assistance: when you're already boarded with us, contact your relationship manager or you can raise a GitHub ticket to get help from other developers. 

Are you missing something from the plugin itself or need additional information? Is there a flow that we can improve? We are keen to hear from you to better our plugin! 

What will change for you? 

For most merchants, this 8-digit extension will have no impact. For a small part of merchants, it could have an impact on your day-to-day operations if you have dedicated processing based on IINs: For example, this affects routing of transactions, identification of the issuer for fee calculation, fraud management and reporting. However, you as a merchant need to be compliant with the new IIN-system at the deadline. If this is not the case, a significant loss in sales due to e.g. rejected cards might result – depending on the implementation. 

What do you have to do?

As a Worldline customer, you don't have to do anything in order to continue using our services. Worldline is already compliant and has updated its products to recognize 8-digit IINs. 

But if you use 3rd party acquirers, 3rd party PSPs or Integrated Software Solutions for your payments, please contact your partners or your terminal supplier. 

Key facts at a glance:

• Generally speaking, if you are not using any rules or processes based on BIN or card number, no action is required from your side.
• On the contrary, if you have access to the card number or if you apply specific rules based on IINs, you should check if these rules are still working with the new 8-digit system.
• If you use the MyCheckout hosted payment pages you are not affected by the change and are thus not required to do anything.
• Solutions provided by Worldline will be fully compliant.

Q&A 8-digit BIN

What is the Bank Identification Number (BIN)?

The Bank Identification Numbers (BIN) uniquely identifies schemes, issuers and holds other payment information. Currently the BIN corresponds to the first 6 digits of the card number.

Because of the increasing demand of BIN by issuers, in April 2022 the length of the BIN will be extended from 6 to 8 digits, without a change of the general length of the card number/PAN - Primary Account Number (e.g. 16 and 19 digits for Visa and Mastercard in Europe).

What is changing?

For Visa and Mastercard, in April 2022 the length of the BIN will be extended from 6 to 8 digits.

By this time, Visa and Mastercard will reallocate the BINs between issuers step by step. Some will keep their complete 6-digits BIN extended to 8 digits, while others will get a slightly or completely new BIN.

What won’t change?

• The general card number length will remain the same.
• The PCI rules won’t change. Receipt requirements remain unchanged.
• No new cards will need to be issued

What can be the consequences?

The use of the old 6-digit BIN could have negative consequences for merchants doing processing on BINs.

The BIN can be used for:

• BIN blocking, fraud scoring, fraud prevention
• Reporting
• Identification of transactions in the context of disputes (chargebacks)
• Loyalty programs
• Information about the type of card (debit, credit, prepaid, commercial) or the currency in use
• Identification of the card issuer (bank and country)

Actions to be taken by you as a merchant?

If you have processing tasks based on BINs, it is recommended to check their compatibility with the new 8-digit format.

If you use 3rd party acquirers, 3rd party PSPs or Integrated Software Solutions, please check with your provider it they are compliant with 8-digit BINs. Worldline has already started to update its products to recognise 8-digit BINs for a readiness in April 2022.

What is the influence on PCI DSS (Payment Card Industry Data Security Standard)?

The generic PCI regulations are not expected to change with the introduction of the 8-digit BIN.

Further questions?

For further questions regarding BIN customisation in relation to your payment solution at Worldline, please contact our customer service team: merchantservices@worldline.com