THREE_D_SECURE_RULES

Type: array of rule objects Default: [] (empty array) Validator: ThreeDSecureRuleSerializer Description: Rule-based conditions that determine when 3D Secure verification is required.

Each rule object has the following structure:

  • klass: Rule class path (string, required)

  • defaults: Rule parameters (JSON object, required)

Available rule classes:

  • omnishop.orders.rules.amount_limit: Requires 3D Secure if transaction amount exceeds specified limit

  • omnishop.orders.rules.masterpass_amount_limit: Amount limit for Masterpass transactions

  • omnishop.orders.rules.check_pos_slug_three_d_only: Requires 3D Secure for specific POS terminals

  • omnishop.orders.rules.trial_limit_per_user_email: Requires 3D Secure after N failed attempts per email

  • omnishop.orders.rules.trial_limit_per_remote_addr: Requires 3D Secure after N failed attempts per IP

  • omnishop.orders.rules.only_guest_user: Requires 3D Secure for guest users only

  • omnishop.orders.rules.is_first_order: Requires 3D Secure for first-time purchasers

  • omnishop.orders.rules.payment_currency: Requires 3D Secure for specific currencies

Rule evaluation:

  • Only evaluated if THREE_D_SECURE_ENABLED is true

  • Rules are evaluated in array order

  • If ANY rule returns true, 3D Secure is required

  • If ALL rules return false, 3D Secure is not required

Example configuration:

Used in: CreditCardConfirmationPage via check_three_d_secure() function to evaluate rule-based conditions

Last updated

Was this helpful?