Retrieve Enabled Payment Methods:

Use the /merchant/details API in the Novalnet Admin Portal to get a list of enabled payment methods for your account. Please note that this is an optional step and if you are already sure about the payment buttons or payment method options you want to offer, you can skip to the third step.

Display Payment Methods:

Based on the response from Step 1, display the available payment methods on your checkout page.

Collect Necessary Prerequisite Data:

Before making a direct API request, ensure you gather all required information to complete the transaction successfully. Payment methods such as credit/debit cards or digital wallets like Apple Pay or Google Pay may require an additional preliminary step to collect card details or secure information from the customer before processing the payment. Please refer to the relevant payment method integration documentation for guidance on implementing these additional steps.

Collect the Necessary Customer and Order-Related Information:

For various payment-related processes, ensure you have prepared the following data: customer name, billing address, customer number, order amount, currency, and order number. Note that not all parameters are mandatory. Refer to the documentation for a complete list of parameters and determine which ones are relevant based on your business needs.

Initiate the API Call:

Once you have prepared the necessary parameters, you can initiate a payment request to the Novalnet server for processing. The Direct API supports two payment flows depending on the payment method: direct or redirected payment mode.
- Direct Payment Methods: Methods such as Direct Debit SEPA or Purchase by Invoice do not require additional authentication steps or explicit login. These payments are processed directly without further customer interaction.
- Redirection Payment Methods: Methods like online bank transfers require the customer to log in to their bank account to complete the transfer. For these methods, you must include additional parameters such as transaction.return_url and transaction.error_return_url to specify where the customer should be redirected after the payment process. For complete handling of redirection payment methods, refer to the provided link for more information.
Additionally, you can choose between the /payment or /authorize endpoints depending on whether you need to collect the funds immediately or later. The /payment endpoint processes the payment immediately, while the /authorize endpoint reserves the funds and allows for capture at a later time.

Handle Notification Webhooks:

Process and respond to notification webhooks to keep your system updated with the latest transaction details. Ensure that your system correctly interprets and acts on the information provided in the webhook notifications to maintain accurate and current transaction records.

Resources Dashboard