Interact Page

The Interact Page within the Subscrypts dApp allows users — particularly merchants and advanced community managers — to directly communicate with the Subscrypts Smart Contract Suite.

It functions as an on-chain console for executing contract functions through an embedded ABI interface (SubscryptsABI-v1.json), removing the need for developers to use external tools like Etherscan or Remix.

This section explains how to use the Interact page, what it supports, and how it bridges user-friendly controls with full smart contract flexibility.

Purpose of the Interact Page

While most Subscrypts dApp users interact through simplified UI flows (e.g., “Create Plan” or “Subscribe” buttons), the Interact page is designed for those who want deeper control and direct access to all available contract methods.

Typical use cases include:

• Testing new contract functions during development.
• Viewing real-time contract data not shown in the dashboard.
• Verifying ABI responses and events for audit purposes.

🧠 The Interact page reads directly from the verified contract ABI and provides a real-time, wallet-connected interface to the blockchain.

How It Works

1. Load ABI Functions: Upon opening the Interact page, the dApp loads all available methods from SubscryptsABI-v1.json.
2. Select Function: Users select a contract function from a dropdown menu categorized by facet (e.g., FacetSubscription, FacetAdmin, FacetPaymentUSDC, FacetView).
3. Input Parameters: The interface dynamically displays all required parameters for the chosen function.
4. Execute or Query:
   • Read-only (view) functions can be executed without gas fees.
   • Write (state-changing) functions prompt a transaction through the user’s wallet.
5. Output & Response: The function output, transaction hash, or event logs appear in a results window for review.

All interactions follow the same non-custodial security model: transactions are only executed once the user confirms them in their wallet.

Interface Overview

The Interact page is divided into three sections:

1. Function Selector

A list that list all available contract functions.

2. Parameter Form

Each function dynamically generates input fields for its parameters (string, uint256, bool, etc.). For example:

Function: planCreate(uint256 price, uint256 interval, string memory name)

Would render as:

Price (in SUBS): [________]
Interval (in seconds): [________]
Plan Name: [________]

3. Result Output

After executing a function, the Interact page displays:

• Transaction hash (for write operations)
• Function return data (for read operations)
• Decoded event logs

A link to Arbiscan is automatically provided for verification.

Example Use Case: Creating a Plan

Instead of using the “Create Plan” page, a merchant could use the Interact page to manually create a plan by calling the underlying function:

planCreate(uint256 price, uint256 interval, string memory planName)

Steps:

1. Select FacetSubscription → planCreate.
2. Enter the price in SUBS, interval in seconds (e.g., 2592000 for 30 days), and a descriptive plan name.
3. Confirm the transaction in your wallet.
4. The dApp displays the transaction hash and emits the _planCreate event.

💡 Ideal for developers testing custom configurations or performing batch creations via external scripts.

Example Use Case: Reading Subscription Details

You can also retrieve active subscription data using getSubscription(subscriptionId) from FacetView:

1. Select getSubscription.
2. Enter the subscription ID.
3. Click Execute.
4. The result displays key data, such as subscriber address, next renewal date, and plan ID.

{
  "subscriber": "0x8Ed1...3fd27",
  "planId": 42,
  "nextPayment": 1733030400,
  "autoRenew": true
}

No gas fees are required for view operations.

Advanced Operations

The Interact page supports more advanced smart contract operations for power users:

Each function is accompanied by clear tooltips describing parameters, access level, and expected result.

Access Control

While most Subscrypts smart contract functions are public and can be called by anyone, a limited number of administrative or system-level functions are restricted using access control modifiers.
These modifiers enforce role-based permissions at the contract level to protect sensitive operations.

Restricted Functions and Their Modifiers

All other functions — including those related to plan creation, subscriptions, payments, and view operations — are publicly accessible and permissionless by design.

If a user attempts to call a restricted function without the required role, the contract reverts with an access error. The dApp captures this gracefully and displays a clear, readable message in the interface.

For more information on how access permissions and output handling are implemented, see Access Control & Outputs.

Example Architecture Diagram

Data Validation and Feedback

The dApp validates user input against the ABI before execution:

• Ensures required fields are filled.
• Checks number formats and address validity.
• Prevents calls to non-existent functions.

Upon completion, feedback is provided as:

• ✅ Success: Function executed, transaction confirmed.
• ⚠️ Warning: Read-only call returned empty or unexpected data.
• ❌ Error: Transaction reverted or invalid parameters.

All feedback includes clear error messages and, for write functions, a direct Arbiscan link.

Integration with ABI Reference

All function names, descriptions, and parameter definitions in the Interact page are derived from the Subscrypts ABI Reference. This ensures one-to-one accuracy with the deployed contracts.

Developers can cross-check function details directly in the ABI documentation for a deeper understanding of their logic.

Summary

What’s Next

Continue to Smart Contract Functions to explore how each dApp action corresponds to specific functions within the Subscrypts Smart Contract Suite.

For reference, visit:

• Subscrypts Homepage
• MiCAR Whitepaper
• Smart Contract Suite Overview