One-Click Payments / Tokenization
Customer-friendly payment processes
Customer-friendly payment processes
Novalnet offers you a secure and elegant way to reuse already processed payment and customer data for subsequent purchases by your customers, thus facilitating the entire checkout process with a one-click solution. Loyal customers in particular appreciate this service, as they do not have to enter their payment information again and again.
One-click payments make shopping in your online shop easier for your customers. You are probably already familiar with this option from providers such as Amazon. Overall, this can significantly reduce the abandonment rate.
No direct processing and storage of payment data takes place at your end as a merchant. When the data is entered for the first time, we create a payment reference (“payment_ref”), also known as an alias or token, with a validity date and customer reference (“customer_no”) and return it to the merchant’s system in real time. By simply transferring these parameters, the merchant can initiate further bookings for the respective end customer at any time during subsequent transactions without the end customer having to enter their data again each time. The end customer can change his or her stored data at any time through different variants (URL, API, etc.). This procedure is also known as tokenisation. Using this payment reference, the merchant can make subsequent bookings without any interaction on the part of the end customer.
Zero postings, i.e. transactions with the amount 0, are used when the end customer’s account is not to be debited at the first posting, but his data and payment details are still to be checked. As soon as his account is really to be debited later, he does not have to enter the payment data again or take any other action. Instead, it is sufficient for the merchant to hand over the payment reference.
Instead of the payment reference, there is another option: you process a normal transaction with the real amount and then store the transaction ID (TID) of the successful transaction in your system. This option allows you to charge your customer further amounts at a later date without having to re-enter the payment details.
Whenever you want to make further transactions later, you can give us the Novalnet transaction ID (TID) of the first successful transaction of this end customer without having to transmit payment details such as the bank account or credit card data.
All relevant data (partially obscured payment data, e.g. for credit cards the first 6 and last 4 digits as well as the expiry month and year or for SEPA direct debits the IBAN) as well as other information is returned to the merchant’s system in real time.
The most important point with both variants, with the payment reference procedure as well as with the use of the origin TID, is, as already mentioned, that you as a merchant do not have to worry about the processing and storage of the payment data. This is done by Novalnet. This process therefore fully complies with the PCI-DSS standards and you do not need your own PCI-DSS certificate.
Hotline: +49 (0)89 - 9230683-29 (Mon - Fri 9 am - 4 pm (CET))
Cookie | Duration | Description |
---|---|---|
wpEmojiSettingsSupports | Session | WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. |
rc::c | session | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
__cf_bm | 1 hour | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
cookielawinfo-checkbox-necessary | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Necessary" category. |
cookielawinfo-checkbox-non-necessary | 1 year | GDPR Cookie Consent plugin sets this cookie to record the user consent for the cookies in the "Necessary" category. |
rc::a | never | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
Cookie | Duration | Description |
---|---|---|
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_gid | 1 day | Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website's performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously. |
_gat_gtag_UA_* | 1 minute | Google Analytics sets this cookie to store a unique user ID. |
_gat_UA-* | 1 minute | Google Analytics sets this cookie for user behaviour tracking.n |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |