Pump Up hosted agents connect to candidate Gumroad API integrations or supplied transaction exports to evaluate ecommerce operations including refund eligibility, revenue reconciliation exceptions, and paid member support requests. The agent inspects sales records, queries non-mutating license verification records, compares platform fees and remitted taxes, and drafts structured recommendations, while designated business owners retain explicit decision authority for authorizing refunds, posting ledger adjustments, and approving subscription cancellations.
2 related templates
Finance and compliance
Decide the refund from the purchase, policy and actual history.
Stripe, Shopify, Help Scout, Paddle, Crisp, Gorgias, WooCommerce, Gumroad, Lemon Squeezy
View templateCustomer success
Resolve the member request against their actual entitlement.
beehiiv, Ghost, Stripe, Paddle, Gumroad, Lemon Squeezy
View templateOperators at digital commerce businesses, software creators, and membership managers evaluating candidate Gumroad workflows for product sales and recurring subscriptions.
In a fictional illustrative scenario, a customer requests a refund for a $149 digital software toolkit purchased 18 days earlier, citing technical incompatibility. The agent queries Gumroad candidate sales records to confirm transaction authenticity, purchase timestamp, and gross amount. To inspect license status without mutating evidence, the agent calls the license verification endpoint with increment_uses_count set to false, confirming the license remains active and valid with 42 historical verifications recorded prior to the review. Because Gumroad verification records reflect API validation calls rather than verified client application usage or device telemetry, the agent reports that actual software utilization cannot be determined from platform records alone. The agent presents an exception summary with the verified purchase timestamp, non-mutating license check, and highlighted telemetry limitations. The customer support lead reviews the unresolved usage uncertainty, determines that the refund window policy applies without disqualifying usage evidence, and authorizes a full refund via the sales dashboard drawer.
While Gumroad OAuth defines scopes such as refund_sales and edit_sales, production automated agents generally treat financial mutations as sensitive operations requiring human authorization. In practice, operators either review agent-staged exception packets and complete refunds manually in the Gumroad sales drawer, or configure an authorized payment gateway connector where approved by policy. Pump Up agents prepare the verified refund packet and await explicit human approval.
Because Gumroad acts as the Merchant of Record, it calculates, collects, and remits global sales tax and VAT on behalf of creators. Consequently, gross customer payments include taxes and platform fee percentages that do not reach the creator bank account. Financial reconciliation workflows must disaggregate gross sales, Gumroad platform fees, payment processing charges, and remitted tax withholdings before comparing net disbursement summaries against bank deposits.
Gumroad provides a Ping notification service and Resource Subscriptions that send HTTP POST payloads for events such as sales, refunds, disputes, and cancellations. Because standard webhook notifications arrive as form-encoded POST requests without default cryptographic signature headers, recipient services typically secure endpoints using URL secret parameters and perform an authenticated read-back against the Gumroad sales or subscriber API to verify transaction legitimacy and deduplicate events.