Skip to Content
DocumentationActionGuidesAccept PaymentsOverview

Payment Overview

Momen payment capabilities let you collect payments and process refunds through built-in payment actions. Configure payment actions on the frontend (Web and Native App) and business logic in backend Actionflows to complete your monetization loop.

Available on Basic and Pro plans only. If your plan expires, payment features stop working. Renew on time.

Supported payment gateways

Momen integrates the following payment capabilities:

  1. Stripe: One-time payments, subscriptions, and more for Web and Native App clients.
  2. Airwallex: International payments, multi-currency transactions, and subscription renewals.

Choose the guide that matches your business scenario and client platform.

Activate payment

Before configuring any gateway, Momen requires you to bind an Order table and activate payment.

Momen does not impose special requirements on order table fields—you can define them freely. For better integration, include at least amount and status fields and relate the table to the account table.

After activation, the system automatically:

  • Creates three system tables:
    • payment_record (1:N with the order table): Records every payment transaction.
    • recurring_payment: Records subscription status.
    • refund (1:N with payment_record): Records every refund transaction.
  • Creates preset Actionflows: Based on activated gateways, the system generates backend webhook Actionflows (e.g., payment/refund callbacks, subscription renewals).

All payment products share the same Order table. Once bound, the Order table cannot be changed or deleted unless you fully disable payment in the configuration panel, clear all data, and rebind.

How payments work

Payment actions include one-time payment and refund. Understanding the full flow helps you configure payments correctly.

Momen handles the gateway communication and callback verification. You configure three parts:

  1. Trigger One-time payment or Refund actions on frontend pages.
  2. Handle the business logic in the corresponding backend Actionflows.
  3. Query the final result on frontend pages.

Clear and disable payment

A Clear and close button appears in the top right of the payment configuration page. Use it with extreme caution.

⚠️

About “Clear and close”

Executing Clear and close completely disables payment. This is a highly destructive and irreversible operation:

  1. Erase sensitive configuration: Clears all gateway API keys, merchant IDs, and related credentials.
  2. Destroy data tables: Deletes the system-generated payment_record, recurring_payment, and refund tables and their relations. After publishing, online historical data in these tables is permanently removed.
  3. Remove action logic: Deletes all preset payment Actionflows and callback Triggers. All logic bound to payment actions becomes invalid.

Note: Reactivating payment creates a new set of tables, Actionflows, and Triggers with no link to previous data.

Last updated on