Pi Subscription dApp

Network: testnet | Contract: CCUF75B6W3HRJTJD6O7OXNI72HGJ7DERZ5MUNOMFMSK23ME5GUIKPFYV

Contract info

Retrieve details of the Pi subscription contract deployed on testnet.

Service info

Retrieve details of a registered service by its ID, including price, period, trial period, and approval periods.

Get merchant services

List all services registered by a merchant on the subscription contract.

Get merchant subscriptions

List all subscriptions for merchant's services. Optionally filter by a specific service ID. The query is simulated as the merchant.

Register service (merchant)

Register a new subscription service on the contract. The merchant sets the service name, price, billing period, trial period, and number of periods to pre-approve.

Transaction will be signed with the merchant secret seed configured in the server environment. The merchant address provided in this form must match to the merchant secret seed configured in the server environment.

Process payments (merchant)

Charge subscribers for a service. The merchant specifies the service ID and a range of subscriptions to process (offset and limit).

Transaction will be signed with the merchant secret seed configured in the server environment. The merchant address provided in this form must match to the merchant secret seed configured in the server environment.

Subscribe

Subscribe to a service by its ID. The subscriber specifies the number of billing periods to pre-approve and whether to auto-renew.

Transaction will be signed with the subscriber secret seed provided in this form. This approach is not secure and used only for testing purpose. For production, check for signTransaction(xdr) support from Pi SDK.

Get my subscriptions

Returns all subscriptions for a subscriber across all merchants and services. Optionally filter by service ID or merchant address. The query is simulated as the subscriber (requires the subscriber's address).

Lookup address

Enter a G... account address or C... contract address. Account Pi balance is retrieved from the token contract via RPC.

Transaction result

Enter a transaction hash returned by Register service, Process payments, or Subscribe. The status and decoded return value are retrieved from the RPC.