WoltLab Cloud VieCode Shop: Integration of paysafecard (Manual Processing) 1.0.2

Accept paysafecard PINs easily in your VieCode Shop and process them manually without external service!

Notes on this plugin

  • You can configure how many paysafecard PINs can be entered. This allows optionally the combination of several paysafecard PINs.
  • This plugin does not use an external API to validate or process the paysafecard PINs entered by the purchaser. Therefore, after entering the paysafecard PINs, the status of the order changes from "Awaiting payment" to "Payment is being processed". This does not yet activate the order! This means that an administrator must first check the order in the ACP, process the paysafecard PINs and then manually activate the order so that the purchaser receives the product they have purchased.


  • You must have WoltLab Suite™ Core 3.1, 5.2 or 5.3 installed.
  • You must have VieCode Shop 7.2 installed.

Installation and initial setup

You can install this plugin as normal and configure it in the same way as the payment connection settings of other VieCode plugins.

After purchasing in the Plugin-Store of WoltLab

You can register at Krymo Software and link your created account with your WoltLab account, so that you will be automatically granted access to the product support within few minutes.

This might also interest you...


  • Version 1.0.2

    Notable Changes

    • The server-side validation of paysafecard PINs has been improved.
    • Empty paysafecard PIN fields were stored in the database as empty paysafecard PINs and were therefore displayed incorrectly in the order details in the ACP.
    • Submitting paysafecard PINs now triggers the shop notification "Payment Verified", if it has been set up previously. You can specify software.krymo.woltlab.viecode.shop.payment.paysafecard.manual as condition, so that the shop notification "Payment Verified" is only triggered for this payment method.
  • Version 1.0.1

    Notable Changes

    • If multiple paysafecard PINs were allowed to be entered, it was required to fill in each PIN field due to an error. This is now optional.
  • Version 1.0.0

    Initial release

Customers Who Bought This File Also Bought