By Transaction ID | Novalnet Docs

 By Transaction ID

Retrieve all the information related to the transaction using the unique identifier from Novalnet - transaction ID (TID).

Header Authentication

To authenticate your payment requests, use Novalnet's custom header authentication. The custom header field is constructed as follows:

  1. Each header request is built using the Payment access key. To get your Payment Access Key, login to your Novalnet Admin Portal and navigate to the path Projects -> [Select Desired Project] -> API credentials -> Payment access key.
  2. The Payment Access Key should be encoded using a variant of Base64.
  3. The resultant base64_encoded value should be passed in the Novalnet's custom header key X-NN-Access-Key.
    The custom header field is formulated in the format
    X-NN-Access-Key:base64_encoded_value.

All requests must be carried out through an HTTPS connection along with the header values, otherwise, the request will fail with authorization error messages.

Your Payment Access Key carry many privileges, so be sure to keep them secure! Do not share your secret Payment Access Key in publicly accessible areas such as GitHub, client-side code, and so forth.

HTTP request headers

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/transaction/details

Parameter List

Each request is separated into so-called objects which indicate an entity

Each parameter is marked with attributes Mandatory, Conditional, 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.
transaction
Object
custom
Object
result
Object
transaction
Object
marker
String
Optional
DEF20140103987 A unique tag used in the APIs to group specific transactions across customers, projects for statistical overview or filtering in reporting. For example, if the transactions that were placed in the store with a particular offer need to be grouped separately, then passing this parameter with a value of "FESTIVALOFFER" can allow you to list these transactions distinctively. identifiers
Multi-Dimensional Array
The identifiers is used to tag and group transactions in a flexible way, similar to the marker parameter but with support for multiple categories. Each identifier consists of a type and a value, allowing transactions to be grouped or filtered across different dimensions (e.g., offers, customer segments, projects).
Hide child object
value
String
Conditional
FESTIVAL|B2B Defines the corresponding identifier within the selected type.

  • Ex: If type = "OFFER", then value could be "FESTIVAL".
  • Ex: If type = "CUSTOMER_TYPE", then value could be "B2B".
Note: Allowed characters include alphanumeric letters (A–Z, a–z, 0–9), underscores (_), hyphens (-), spaces, periods (.), and accented characters such as umlauts (ä, ö, ü). The maximum permitted length of this parameter is 70 characters.

bank_details
Object This object contains the bank details to which the customer has to transfer the transaction amount
Hide child object
bank_code
Integer
Conditional
74020100 Bank code bank_name
String
Conditional
Raiffeisenlandesbank O Zndl Sddeutschland Bank name bank_place
String
Conditional
Passau Place of the bank account_holder
String
Conditional
Max Mustermann Name of the bank account holder iban
String
Conditional
DE24300209002411761956 IBAN (International Bank Account Number) of the bank account holder bic
String
Conditional
CMCIDEDDXXX BIC (Bank Identifier Code) of the bank account holder qr_image
String
Conditional
https://nnt.ag/epcqr/15339600072003130.png This parameter provides a hosted link to a dynamically generated QR code for applicable Pay-By-Invoice transactions. The QR code is created for all pending, authorized, and successful transactions (including subscriptions and instalment renewals) when the transaction amount is greater than zero.

For marketplace transactions, a single QR code is generated for the total order amount. If the transaction amount or order number is modified, the QR code is automatically regenerated and updated on the same link to always reflect the latest transaction details.
fraud_check
Object This objects contains the Fraud check details, for example: Buergal score
Hide child object
trader_name
String
Mandatory
Mustermann GmbH Trader name belonging to this VAT ID trader_address
String
Mandatory
Musterstr, 2, 12345, Musterhausen Trader address belonging to this VAT ID buergel_score_value
String
Optional
0 The resultant CRIF Buergel Score value from the fraud check
partner_payment_reference
Integer
Conditional
999999919 The payment reference for the Multibanco payment type. Using this reference, the customer pays in online portal or in the Multibanco ATM to complete the purchase service_supplier_id
Integer
Conditional
11854 Service supplier ID from Multibanco hook_url
String
Conditional
https://www.demoshop.de/webhook Notification/Webhook URL to receive the information about the notification events that occurs for each transaction. To know more about the notification and events, refer this section. tid_payment
Integer
Optional
12997200005200690 The original payment TID which will be sent during the transaction response status_code
Integer
Mandatory
100 Status code for the transaction credit_reason_1
String
Optional
www.test.com The credit reason1 defines the text on the customer's proof of payment credit_reason_2
String
Optional
Test Product The credit reason2 defines the text on the customer's proof of payment credit_reason_3
String
Optional
ABC Company The credit reason3 defines the text on the customer's proof of payment order_date
String
Conditional
2021-06-10 Original purchase date, for which the cashback or transaction is being processed

Note: The format to be specified is "YYYY-MM-DD". order_amount
Integer
Conditional
2000 Original purchase amount, for which the cashback or transaction is being processed order_reference
String
Conditional
XXXYYYZZZ Original purchase reference or order number, for which the cashback or transaction is being processed credit_reason_4
String
Optional
INV-1234 The credit reason4 defines the text on the customer's proof of payment authorization
Object
Hide child object
auto_action
String
Conditional
CAPTURE|VOID It contains the action (CAPTURE/VOID) going to be carried out on the expiry of the authorization.Note: Merchant can customize these action on Novalnet Admin Portal.
mandate_ref
String
Optional
NN-12345678901234567 Unique mandate reference of the written SEPA mandate, this reference will be displayed in the end-customer's bank statement. If not provided, by default TID will be considered mandate_date
String
Optional
2026-08-21 Start date at which the end-customer allowed Novalnet or the merchant to book from his/her account. The date of signature of SEPA mandate. If not provided, by default the transaction date will be considered.

Note: The format to be specified is "YYYY-MM-DD".

invoice_no
String
Optional
852963 Unique identifier invoice number from the shop partner_payment_url
String
Mandatory
https://pagar.wepayout.co/?hash=XXXXXX The payment reference for the Boleto payment type. It contains the bank slip URL. debit_reason_1..5
String
Optional
www.test.com The debit reason defines the text on the customer's proof of payment (e.g., bank statement records and similar).Note: Each debit reason can have a maximum of 27 characters, with an overall length of 140 characters for all five debit reasons. The debit reason is case-sensitive, allowing characters from a to z, A to Z, and 0 to 9. Only space and hyphens are allowed, while other special characters and symbols are taken as spaces.
merchant
Object
customer
Object
customer_ip
String
Mandatory
127.0.0.1 Customer's IP address customer_no
String
Optional
12345 Customer's unique identifier from the shop birth_date
String
Optional
1992-06-10 Customer's date of birth. The format to be specified is "YYYY-MM-DD"

Note: Mandatory only for B2C for processing guaranteed and installment payments such as GUARANTEED_DIRECT_DEBIT_SEPA, GUARANTEED_INVOICE, INSTALMENT_DIRECT_DEBIT_SEPA, INSTALMENT_INVOICE

tel
String
Optional
+49 089 123456 Customer's telephone number mobile
String
Optional
+491747781423 Customer's mobile number fax
String
Optional
+49 89 654321 Customer's fax number shipping
Object This object contains the customer's shipping information
Hide child object
first_name
String
Optional
Max Customer's shipping firstname last_name
String
Optional
Mustermann Customer's shipping lastname email
String
Optional
test@novanet.de Customer's shipping email address company
String
Optional
ABC GmbH Organization name of the shipping address house_no
String
Optional
2 Customer's shipping house extension street
String
Optional
Musterstr Customer's shipping street name city
String
Optional
Musterhausen Customer's shipping city zip
String
Optional
12345 Customer's postal code country_code
String
Optional
DE Customer's shipping country. The two-character country ISO code as defined in ISO-3166-1 alpha-2 tel
String
Optional
+49 089 123456 Customer's shipping telephone number mobile
String
Optional
+491747781423 Customer's shipping mobile number state
String
Optional
Berlin The customer's shipping state identifies a specific region within a country. Novalnet currently supports this parameter in three formats:
  • ISO 3166-2 State Codes: Provide the state using the state code according to the ISO 3166-2 standard for seamless transmission during payment processing. For example, state codes (such as "BE" for Berlin) are typically 2 characters long.
  • Country Code Format: The state code in country code format for Germany is "DE-" followed by the 2-letter state code (e.g., "DE-BE" for Berlin, "DE-HH" for Hamburg).
  • Full State Names: Full state names can be provided using string characters with a maximum length of up to 50 characters (e.g., "Berlin", "Hamburg").
Note: Allowed characters are alphanumeric, numbers, space, hyphen, apostrophe, period and other accented characters such as umlauts, Latin characters. district
String
Optional
Pankow The customer's district from the shipping information, which identifies a specific administrative region within a state or province.

Note: Allowed characters are alphanumeric, numbers, space, hyphen, apostrophe, period and other accented characters such as umlauts, Latin characters.

vat_id
String
Optional
DE123456 Organization's VAT ID tax_id
String
Optional
123/123/123 The parameter represents the unique tax identification number assigned to a customer or company. This is essential for compliance with tax regulations and enables accurate identification of businesses in B2B transactions.Note: Allowed characters are alphanumeric, numbers, space, hyphen and period. reg_no
String
Optional
HRB1234 Organization's registration number session
String
Optional
fedgrgst5653653hdgfsvgdsf622627e Customer's session ID from the shop no_nc
Integer
Optional
1 This parameter will be returned, If you opted for no_nc option
subscription
Object
instalment
Object
marketplace
Object
invoicing
Object
custom
Object
collection
Object
reminder
Object