Stripe Payment

Set Up a Stripe Account

• Sign up for or log in to your Stripe account .
• Retrieve your Publishable Key and Secret Key from the Stripe Dashboard.

Activate Stripe Payment

• Go to Settings → Payment and activate the payment module.

Upon activation, the system will automatically:

• Create three backend tables:
  • payment_record: Stores one-time payment records.
  • recurring_payment: Manages subscription billing.
  • refund: Tracks refund transactions.
• Generate four system Actionflows:
  • StripePayment: After a successful one-time payment
  • StripeRefund: After a successful refund
  • StripeRecurringPaymentManagement: When starting or canceling a subscription
  • StripeRecurringPaymentDeduction: When Stripe automatically charges for subscription renewal

Configuration	Configuration

These system-generated Actionflows securely handle backend payment event processing.

Configure Stripe Credentials

Navigate to Settings → Payment → Stripe.

• Enter the keys from your Stripe account:

• Enter your brand name, brand logo, and brand slogan.

Configure Stripe Webhooks

Follow these guidelines to ensure your Stripe Webhook integration is set up correctly and reliably.

1. The Auto-Generated ‘Payment Success’ Webhook

When you first set up Stripe payments, our platform automatically creates a webhook endpoint in your Stripe account. This webhook is designed exclusively to handle successful payments.

• Key Rule: Do not modify this auto-generated webhook. Specifically, do not add other events to it from your Stripe dashboard.
• Reason: This webhook is linked to a single actionflow that executes “after a payment succeeds”. If you add other events like charge.failed, it will incorrectly trigger your “payment success” logic for failed payments, leading to critical errors.

2. Listening for Other Payment Events

To handle events other than payment success (e.g., charge.failed, charge.refunded), you must create a new, dedicated webhook for each scenario.

Here is the correct procedure:

• Create new actionflow and webhook trigger in Momen

  • Create an actionflow and set up the webhook trigger.
  • Design the logic for the specific event (e.g., for a charge.failed event, add an action to send a notification email).
  • Once created, copy the webhook URL generated for this actionflow.

• Create a New Webhook Endpoint in Stripe

  • Log in to your Stripe Dashboard and go to Developers > Webhooks.
  • Click “Add endpoint” to create a new one.
  • Paste the webhook URL from our platform into the “Endpoint URL” field.
  • Under “Events to send,” select only the specific event this workflow is designed to handle (e.g., charge.failed).
  • Save and activate the endpoint.

By creating a separate Webhook trigger(Momen) + Webhook Endpoint(Stripe) pair for each event, you ensure your payment logic remains clear, organized, and error-free.

Add Payment Action

Use the Stripe Payment Action to charge users for a single transaction.

Note: To charge $10.00 USD, enter 1000 as Stripe expects the amount in cents.

Configure Post-Payment Business Logic

Stripe automatically triggers backend Actionflows for different payment events.
These Actionflows allow you to parse event data, validate results, and implement custom business logic securely.

• Trigger: After a successful one-time payment
• System actions:
  • Parse payment data (e.g., orderId, paymentStatus)
  • Detect duplicate webhooks using alreadyProcessed (false = first trigger, true = processed)
• Field notes:
  • orderId: The orderId provided when invoking the payment action; use it to locate and update the corresponding order record
  • paymentStatus: SUCCESSFUL for a successful payment, FAILED for a failed one
  • alreadyProcessed: Only treat a payment as failed/succeeded when the corresponding status is returned and alreadyProcessed is false
• Custom logic examples:
  • Update order status to paid
  • Grant access to purchased services
  • Send confirmation emails or notifications

Retrieve Payment Result

Payment operations are asynchronous.
To display real-time results:

• Subscribe to the Payment table using a list component.
• Listen for real-time updates to refresh the frontend dynamically.

Add Refund Action

Use the Stripe Refund Action to process a refund.

Configure Post-Payment Business Logic

• Trigger: After a successful refund
• System actions:
  • Parse refund data
  • Detect duplicate webhooks using alreadyProcessed (false = first trigger, true = processed)
• Field notes:
  • orderId: The orderId provided when invoking the payment action; use it to locate and update the corresponding order record
  • alreadyProcessed: Only process refund logic when alreadyProcessed is false
• Custom logic examples:
  • Update order status to refunded
  • Adjust user benefits or subscriptions
  • Notify the user about the refund

Retrieve Payment Result

Payment operations are asynchronous.
To display real-time results:

• Subscribe to the Refund table using a list component.
• Listen for real-time updates to refresh the frontend dynamically.

Add Recurring Payment Action

Before starting recurring payments:

• Create a Recurring Price object in Stripe and obtain its Price ID.

Recurring actions support:

• Starting a subscription
• Canceling an existing subscription

Configure Post-Payment Business Logic

Stripe Recurring Payment Management Actionflow

• Trigger: When starting or canceling a subscription
• System actions:
  • Update the Recurring Payment Table
• Field notes:
  • status: The current status of the recurring payment. Possible values include INCOMPLETE, INCOMPLETE_EXPIRED, ACTIVE, PAST_DUE, CANCELED, TRIALING, and UNPAID. Use these to control your logic as needed. See Stripe documentation  for details.
• Custom logic examples:
  • Activate or deactivate subscription-based features

Stripe Recurring Payment Deduction Actionflow

• Trigger: When Stripe automatically charges for subscription renewal
• System actions:
  • Insert a new order record
• Custom logic examples:
  • For active subscriptions, add a node to create a new order and pass the generated order ID to the orderId input of the payment creation node.

Retrieve Payment Result

Payment operations are asynchronous.
To display real-time results:

• Subscribe to the Payment or Recurring Payment tables using a list component.
• Listen for real-time updates to refresh the frontend dynamically.