Payment Configuration

Payment Configurations allow users to set up a payment at the end of the forms submission.

🔘 1. No

Payment Configuration disabled (default state)

• Meaning: Payments are completely disabled.

• Effect: No payment fields will be shown or required.

• Use case: If your service/form doesn’t need to collect any payments.

---

🔘 2. Yes

Payment Configuration is enabled with the necessary fields filled out

• Meaning: Payments are always enabled.

• Effect: Users must complete payment.

• Fields shown:

  • Payment Service (e.g., Stripe, PayPal)

  • API Key (for integrating the payment service)

  • Currency

  • Amount

  • Instance (optional or specific to the platform)

• Use case: When every submission requires a payment.

---

🔘 3. Yes Conditionally

Payment Configuration Enabled with 'Yes Conditionally' where if the age is Greater than or Equal to 18 then payment must be made

• Meaning: Payments are enabled only under specific conditions.

• Effect: Payment is requested only if a condition is met (e.g., a specific form field equals a value).

• Fields shown:

  • Condition Field: The field in your form to monitor (e.g., “Age”)

  • Operator: Comparison logic (e.g., greater than, equals, contains)

  • Condition Value: The specific value that triggers the payment (e.g., “18”)

  • Plus all the payment fields from the "Yes" option.

• Use case: When payment is only required for certain users or selections (e.g., only when someone selects a paid service option).