Payment settings – system description

The payment provider settings, adapter state, saving rules, test payment and the data sources of the transaction list.

Overview

Payment provider setup, test payment and the latest transactions. The settings are stored among the module's system settings (provider, webhook secret, merchant id, API key, test mode, vendor company id). Table names carry the installation's own prefix in the database.

Operation

  • View (list, UNMAPPED): the settings, adapter state, webhook and return address, subscription selector, latest transactions (payment.transactions, from payment_transaction).
  • Save (payment.save, edit): the provider must be one of Dlbtpayment::PROVIDERS (manual, simplepay, barion, stripe, paypal); for a non-manual provider the webhook secret is required; the six keys are written over the existing module settings.
  • Test payment (payment.testpay, edit): Dlbtpayment::startCheckout(subscription_id, amount, currency).

Permissions

list: UNMAPPED; edit: not classified. No content scope.

Related topics

Related topics: online payment permissions
Request consultation Back to home
Topics
permissions (15) subscription (6) plan (4) usage limit (4) content permission (3) order (3) function permission (2) background job (2) online payment (2) tenant (2) user (2) user group (1) log (1) credit balance (1) resource quota (1) add-on package (1) reward (1) package family (1) pricing table (1)