Migrate to Batch

Get familiar with Batch, the payment flow and its -specific features.

Batch implements the same core feature like legacy Worldline Batch (advanced): Bulk upload of card data for asynchronous transaction processing.

However, there are some differences to consider when migrating:

You can keep using your existing PREPROD (test) account to get started. To activate in your PREPROD (test) account, follow these steps:

1. Log in to the PREPROD (test) Back Office.
2. Go to Configuration > Account > Your options.
3. In "Available options", look for "DIR (Merchant using Direct integration)" and click on "Activate". 

In addition to this, make sure the Batch option is activated for your account subscription. Contact us to confirm this.

If you cannot find "DIR (Merchant using Direct integration)", then it is activated by default. Look in the "Default options" to confirm. 

You do not have a test account yet? Get one in just a few steps.

You can upgrade to a paid account at any time.

Your account is being created and you will receive a message soon.

Cancel Create an account

Check your mail!

Check aaaaa for a link to set your password. This helps us keep your account secure.

If you cannot see the email please check your spam folder.

What's next?
After you secure your test account, you can build a test integration. The first step is deciding how to link your website with our platform.

Getting started

Ways to integrate

1Use our SDKs

Our Server SDKs wrap the API in a highly efficient and accessible way, allowing you to create your own application easily.

View Server SDKs

2Create custom integrations

Freeing you from any possible dependency, all our REST API endpoints are also directly accessible via a specific authentication process.

View API Reference

Modify the target endpoint URL and the data formatting for processing transactions or maintenance operations.

Target endpoint Urls

Batch via both /legacy use individual API endpoints for individual steps in the batch processing flow.

Batch file format

Legacy batch files are plain text files, with each individual line representing one transaction. Batch via is built upon JSON, requiring you to reformat the data to be sent in your requests. Our dedicated Batch guide provides detailed information, for both general instructions and specific use case.

reduces your efforts by outsourcing most of the Back Office technical settings to the API. However, you need to make some basic configurations in your account:

• Configure your API Key/API Secret to set up the authentication mechanism. Read our dedicated guide to learn how to do this.
• Configure your Webhooks Key/Webhooks Secret to receive feedback for processed transactions. Read our dedicated guide to learn how to do this.

Check out our comprehensive guide to learn about how your existing account settings translate to the API.

You can follow up on Batch transactions through the e-Portal.

The e-Portal offers detailed reporting via:

• Immediate reports for near real-time transaction monitoring and investigation.
• Scheduled reports for recurring reporting, reconciliation, and large-volume data exports.

Available reporting capabilities include:

• Transaction-level reporting.
• Aggregated transaction totals.
• Capture reporting.
• Automated report delivery through SFTP.

Refer to the "Reporting" chapter in the e-Portal guide for more information.

Make sure your webshop infrastructure receives and processes our platform's transaction feedback according to the payment.id logic.

offers webhooks and endpoint GetPaymentDetails to get all information you need to follow-up on your orders.

To enhance transparency, implements three properties to represent a transaction status:

• status
• statusCategory
• statusCode

Check out our comprehensive Status guide for all possible return values, including a mapping of classic parameter STATUS to the aforementioned properties.