Loading Configuration

To load the settings of a Sales Location, a technical integrator can call the 'getConfiguration' endpoint in the Gateway processing namespace.

You will receive all information that the merchant configures that is necessary to build a checkout page. With that data and the authentication details you can process payments via the transaction:gateway unit, or server2server direct payments endpoints.

An integrator that offers their checkout services to third parties (merchants) can certify for different features.

Payer Checkout Features

	Individual integration	Third party integration
getConfiguration	Optional	Mandatory
eCommerce gateway checkout	Mandatory	Mandatory
Point of Sale Terminal transaction	Optional	Options
MOTO card not present transaction	Optional	Options
Send a Paylink (email / sms / manual)	Optional	Optional
server2server CARD based payments	Optional	Optional
ApplePAY & GooglePay button integrations	Optional	Optional
server2server Giftcard Redeem	Optional	Optional

Merchant Checkout Optimalisation

Action	Explanation
MIN / MAX amounts per payment Method	Show only Payment Methods that are in line with the MIN/MAX amount.
Show + More Country Optimiser	Show the Payment Methods & offer the More List.
MandatoryFeeldsChecker	Check pre-checkout the fields that are mandatory based on the selected payment Method
IPFiltering	Show or Hide payment methods and handle the exceptionlist.
Sorting	Rank the Payment Methods based on the comma separated list.
MultiLanguageCheckout	Change the names of the Payment Methods based on the selected checkout language
look&feel mananger	Update the look&feel by using the 4 colours & CSS provided stylesheet.

Hier de recipe over LOAD...

🦉

Create a card based transaction by TOKEN

Open Recipe

Save the configuration

You can save the full JSON response, or save the data in any database of caching engine.