Mit dem wpShopGermany-Modul SOFORT Ident können Sie ausgewählte Produkte einer Altersverifikation unterziehen lassen. Mit Sofort Ident geben Sie Ihren volljährigen Kunden ohne Medienbruch und Verzögerung altersgeschützte Inhalte frei. Weiter führende Links: Tarife für die. thesweetdiabetic.com › datenschutz-sofort-ident.
Datenschutz (Sofort-Ident)thesweetdiabetic.com › datenschutz-sofort-ident. SOFORT GmbH, Die Kommission für Jugendmedienschutz (KJM), die zentrale Aufsichtsstelle für den Jugendschutz im privaten Radio und. Um das TÜV-zertifizierte Verfahren SOFORT Ident aufzurufen, loggen Sie sich bitte zunächst mit Ihren Zugangsdaten in das Kundencenter meincongstar ein.
Sofort Ident Related resources Videonachgehakt: Warum gibt es Prepaid-SIMs nur noch gegen Ausweis?
Passwort vergessen? Bankdetails Bewertungen Kommentare. Logo der Bank:. Details Typ Finanzdienstleister Höhe der Einlagensicherung Nicht vorhanden Land der Einlagensicherung nicht vorhanden Beschreibung Einlagensicherung nicht vorhanden Einlagensicherungssystem nicht vorhanden.
Kommentieren 0. Sofort requires a statement descriptor before the customer is redirected to authenticate the payment.
To allow your customer to authorize the payment, redirect them to the URL provided within the redirect[url] attribute of the Source object.
This happens regardless of whether authorization was successful or not. If your customer declines the payment, the status transitions to failed.
By doing so, your customers are returned to your app after completing authorization. Refer to our Sources documentation for iOS or Android to learn more.
This leads to a Stripe page that displays information about the API request where you can either authorize or cancel the payment.
After the customer authenticates the payment, the status of the source transitions to chargeable and you can use it to make a charge request.
This transition happens asynchronously and may occur after the customer was redirected back to your website. Some customers may close their browser instead of following the redirect and returning to your app or website.
For these reasons you must make sure that your integration relies on webhooks to determine when the source becomes chargeable so that the charge can be created.
Refer to our best practices for more details on how to best integrate payment methods using webhooks. As soon as the source is chargeable, from your source.
After the charge is confirmed—and the funds guaranteed—its status updates to succeeded. Either of the following events are sent when the status of the charge updates:.
We recommend that you rely on these webhook events to notify your customer of their payment status. The risk of fraud or unrecognized payments is low because the customer must authenticate the payment with their bank.
Additionally, if the funds are received after the cut-off date, the customer is automatically refunded. On average, you can expect approximately 0.
This number can vary based on your industry or customer base. Depending on your average payment amount, the type of products or service being provided, and the risk associated with your business, you might prefer to fulfill orders only after you receive the charge.
Payments made with Sofort can only be submitted for a refund within days from the date of the original charge.
If you create a full or partial refund on a pending charge, the refund is performed only after the status of the charge transitions to succeeded.
A source must be used within six hours of becoming chargeable. For this reason, make sure the order is canceled on your end and the customer is notified as soon as you receive the source.
A detailed description of the individual steps is provided subsequently:. Test mode : Activate the test mode during integration. Using the test data specified below, you can test your integration at no transaction costs no Schufa queries are performed here.
Project check: If you check the box "Check project after creation", an employee will subsequently contact you and check the project settings.
For this purpose, you have to redirect the customer to be verified from your website to our input form. Subsequently, we verify the transferred address by the customer login in the customer's online banking.
If successful, we perform a Schufa query for age verification. You will receive the result as a parameter in the next step when the customer is redirected to the return URL defined by you and you can proceed with the next steps in your shop system.
The principle of the responses is the same. Detailed information on the individual API calls and responses can be found in the section "Overview of parameters".
Various parameters must be transferred to our API for the call. Some parameters are mandatory, some are optional. To make sure that this data cannot be changed on its way from your shop system to SOFORT, parts of the message are hashed with the project password and transmitted as a hash value for input verification.
Details on the use of the individual parameters and on the hash value calculation are listed in the overview of parameters.
Please implement the call only via this URL and transfer the required parameters see section "Overview of parameters" ; otherwise an error message will appear.
If you do not transfer your customer's data names, address, date of birth with the redirection, the customer can fill in those data on the input form.
If you block this possibility in the project settings of the merchant area SOFORT backend you need to transfer those parameters with the redirection.
In the next step the customer authentication takes place. In order to do that your customer logs in to the online banking and enters the name, date of birth, and address data.
If authentication has been successful, a Schufa query is performed with the related data. Based on a positive result returned by the Schufa, the age verification result will be determined.
To make sure that this data cannot be changed on its way from your shop system to SOFORT, parts of the message will be hashed with the project password and transmitted as a hash value for input verification.
The resulting hash value must be verified in your shop system before the age verification result is accepted.
Details on the individual parameters and on the hash value calculation are listed in the overview of parameters.
The returned customer data names, address, date of birth are equivalent to those of the input form that might be changed by your customer.
If you have blocked to change those parameters on the input form in the project settings of the merchant area SOFORT Backend the returned data are the same as you initially transferred via the redirection to the input form.
Detailed information on possible statuses and their descriptions can be found in the overview of parameters. If you want to receive a notification on the successful completion of the age verification apart from the return e.
To add a notification, please click "Add new notification". The following notification types are available which are subsequently explained in detail:.
Select "Email". Activate this notification by checking the box "Activated". Then enter an email address and select the language in which the email is supposed to be written.
The HTTP notification calls a programme in your shop system and confirms the successful age verification result.
Every attempt to call the programme on your server is saved in your customer menu. Further information is provided there, e.