Worldline | Transfer Back Office settings

worldline Direct

Sign up

Direct reduces your efforts by outsourcing most of the Back Office technical settings to the Direct API or the Merchant Portal.

Transfer Back Office settings to the Merchant Portal / Direct API

Check out the table for a comprehensive overview:

Back Office module (Configuration > ?)	Impact on Direct integration
Template > Template selection	"eCommerce payment page": Learn in our dedicated guide how to customise the look and feel of the Hosted Checkout Page. "FlexCheckout (tokenization) page": Learn in our dedicated guide how to customize the look and feel of the Hosted Tokenization Page.
Technical information > Global transaction parameters	"Default operation code": Direct ignores this setting. Send property cardPaymentMethodSpecificInput.authorizationMode in your requests instead. If undefined, our platform processes transactions as authorisations by default. "Payment retry": Direct ignores this setting. Send propertyhostedCheckoutSpecificInput.allowedNumberOfPaymentAttempts in your requests instead. If undefined, our platform grants 10 retries. "Default data capture (payment) procedure"/"Processing for individual transactions" are still applicable for Direct transactions.

Technical information > Global security parameters	Direct negates these settings by implementing a different authentication mechanism. See also "API settings".
Technical information > Data and origin verification
Technical information > Payment page	Direct negates these settings. Learn in our dedicated guide how to customize the look and feel of the Hosted Tokenization Page.
Technical information > API settings	Manages Direct authentication/webhooks credentials, which you can also do in the Merchant Portal.
Technical information > Transaction feedback	Direct negates these settings by using webhooks instead.
Technical information > Transaction emails	Not used by Direct.
Technical information > Test info	Not used by Direct. Refer to our test cases guide for test data.