Knowledge Base
Resource Center Hub
Free and member-only business documentation, system blueprints, and AI scripts.
blogBy Perez Systems Team
How to Architect a Multi-Product Software Ecosystem
An in-depth article analyzing the structure, data routing, and RevenueCat checkout models of the Perez ecosystem network.
When building a multi-product ecosystem, the primary challenge is user identity and pricing consolidation. Having separate customer databases for six different services leads to duplication. That is why centralizing your offers inside a master catalog (like the ARS Offer Catalog) and routing transactional signals through a single webhook engine is vital. We utilize REST webhooks to feed transactional details into a single source of truth, updating client metrics dynamically.
sop
SOP: Failed Payment Recovery Sequence
Standard Operating Procedure detailing the automated steps required when a RevenueCat subscription fails.
Step 1: RevenueCat subscription.updated webhook fires with status 'past_due'. Step 2: ARS catches the payload, tags the profile as 'Billing Issue', and disables membership access. Step 3: Trigger a SpeakEasy conversational AI outbound dial to schedule a payment update callback. Step 4: Dispatch automated billing update link via SMS and email. Delay 48 hours before retrying payment.
prompt
Prompt: RevenueCat Webhook Payload Analyzer
Copy-paste system prompt to train LLMs to interpret raw RevenueCat JSON payloads and generate clean human-readable summaries.
System Prompt: 'Act as a senior systems integration engineer. You will receive a raw JSON webhook payload from RevenueCat (PURCHASE or CANCELLATION events). Analyze the payload and extract: Customer Email, Amount Paid, Billing Interval, Purchased Offer ID, and Referral Metadata. Format the output in a clean markdown table, highlighting any discrepancies or empty fields. Do not include raw JSON in the output.'
tutorial
Tutorial: Syncing RevenueCat IDs in 5 Minutes
Video walk-through outline and guide on configuring environment variables to match catalog IDs.
Step 1: Go to your RevenueCat Dashboard -> Products. Step 2: Copy the Product ID (e.g. tpc_plus). Step 3: Open your .env.local file in the project. Step 4: Map the Product ID to the respective catalog entry (e.g. priceId). Step 5: Test the flow using the simulated dev checkout to verify pricing representation. Watch our 5-minute video guide inside the member portal for visual steps.
faq
FAQ: How is the ARS API integration authenticated?
Frequently Asked Question about API security, headers, and local fallback configurations.
Every outbound POST request to the ARS API (such as lead capture or purchase logs) is authenticated via a Bearer token in the request headers (Authorization: Bearer ARS_API_KEY). If the api key or url is missing in staging or local dev, the client prints console warnings and triggers a local fallback mode. This ensures checkout and forms never crash for customers due to external server connectivity issues.