Module API is relevant when you want to use the risk modules without entering into the transaction flow. Typical use case includes:
And as this API does not involve a transaction flow, no transaction will be created, and your account will be charged based on the per-service usage.
To authenticate your module requests, use Novalnet's custom header authentication. The custom header field is constructed as follows:
X-NN-Access-Key:base64_encoded_value.All requests must be made through an HTTPS connection along with the header values. Otherwise, the request will fail with authorization error messages.
Your Payment Access Key carries many privileges, so keep them secure! Do not share your secret Payment Access Key in publicly accessible areas such as GitHub, client-side code, etc.
|
X-NN-Access-Key
|
base64_encode({PAYMENT_ACCESS_KEY}) |
|
Content-Type
|
application/json
|
|
Accept
|
application/json
|
|
Charset
|
utf-8
|
End point URL: https://payport.novalnet.de/v2/module
Each request is separated into so-called objects which indicate an entity
Each parameter is marked with attributes Mandatory, Optional. Based on your necessity, you can use these parameters accordingly.
- Icon denotes the parameter is used on the conditional attribute basis, and hovering on this icon will give you the details about that condition.
- Icon denotes the payment methods supported or relevant to the parameter defined, and hovering on this icon will give you the details of the list of payment methods supported.