Jepely is a Software-as-a-Service (SaaS) cloud architecture providing AI chatbot deployment models and social media communication automation tools. This Payment & Billing Policy regulates the automated invoicing routines, subscription structures, renewal configurations, and payment processing behaviors handled within the Jepely engine. Accessing premium dashboards or clearing system-generated invoices implies absolute acceptance of these terms.
WhatsApp services provided through Jepely may involve two separate billing components: Jepely subscription fees and WhatsApp usage charges imposed by Meta.
Jepely subscription fees cover access to the selected Jepely software features and service infrastructure, including applicable WhatsApp CRM, chatbot, automation, and API functionality according to the purchased product or subscription plan.
Jepely subscription fees are separate from any charges imposed by Meta for WhatsApp usage. Payment for a Jepely subscription is processed through an independent third-party payment gateway selected by Jepely.
A Jepely subscription becomes active after Jepely receives and successfully validates the payment confirmation or callback from the applicable payment gateway. The corresponding client service access is then activated according to the purchased product and subscription period.
WhatsApp messaging may be subject to fees determined and charged by Meta under the applicable WhatsApp Business Platform pricing, policies, and billing arrangements.
Such WhatsApp usage charges are not included in the Jepely subscription fee unless explicitly stated otherwise on the applicable product or checkout page. Where Meta charges apply, the applicable billing relationship remains between the user's own WhatsApp Business Platform account, Business Portfolio, or WhatsApp Business Account and Meta.
Jepely does not currently act as the billing intermediary for Meta WhatsApp message charges. Jepely does not collect, settle, or add Meta's WhatsApp usage charges to the Jepely subscription invoice.
Users are responsible for maintaining a valid payment method and billing configuration with Meta for their WhatsApp Business Platform usage. Any pricing, billing category, usage calculation, or charge applied by Meta is governed by Meta's own terms, pricing structure, and billing system.
Jepely may provide WhatsApp functionality through multiple application layers, including:
The availability of these Jepely features is governed by the user's active Jepely subscription and applicable service limits. Their availability does not change the separate billing relationship for WhatsApp usage charges imposed by Meta.
Meta may change its WhatsApp Business Platform pricing, billing categories, policies, or applicable charges independently of Jepely. Such changes do not automatically constitute a change to Jepely subscription pricing.
Users are responsible for reviewing applicable Meta pricing and billing information for their WhatsApp Business Platform account.
Jepely does not directly process or store users' payment card or banking credentials. When purchasing a Jepely subscription, users are redirected to a checkout environment operated by the applicable third-party payment gateway.
The payment flow generally follows this sequence:
Jepely receives payment status information from the payment gateway through its supported notification or callback mechanism. A subscription is activated only after the payment status has been successfully validated by Jepely.
Payment card numbers, security codes, and other sensitive payment credentials are handled by the applicable payment gateway and are not intentionally stored by Jepely.
The platform generates an official system invoice the instant a user checks out a pricing plan. Every invoice carries a strict built-in timestamp token. If checkout clearings are not completed before token expiration, the invoice automatically voids inside the database cluster, requiring a new checkout session.
SaaS premium resources are automated to turn active the instant a valid network **payment callback** is received from our clearing provider. While service authorization is typically real-time, occasional background network load may introduce slight processing handshakes.
In exceptional situations where a financial platform clears funds but network drops trigger a callback failure, access configurations may require manual intervention. Users are strongly urged to keep digital receipt screenshots or invoice vouchers until their tier access updates. To force reconciliation, users must open an urgent ticket containing their Invoice ID and Transaction ID. Our team resolves verified clearings within 1 to 2 business days.
Plans carry distinct runtime limitations (e.g., 30-day intervals, 365-day enterprise cycles). Timelines map an `expired_at` timestamp structural field. The exact moment expiration markers hit the database, automation workflows are instantly paused, AI chatbot agents turn offline, and external API webhook lines freeze until a successful renewal checkout occurs.
Dashboard account operators hold sole responsibility for renewing subscription tiers prior to system expiration dates. Jepely assumes zero liability for business data tracking gaps, unhandled incoming Facebook/Instagram client comments, or paused customer loops resulting from late renewals.
Users can instantly scale up their configuration plan within the same system product group. Upgrades trigger an automated **prorated balance calculation** that evaluates your remaining timeline value:
This calculated dynamic remaining metric is systematically deducted from your new package checkout total.
To protect current configuration datasets, downgrades cannot take place mid-cycle during an active billing block. Downgrade requests are scheduled to take effect at the turn of the next billing cycle.
Platform costs are explicitly outlined on our check-out grids and may display in Indonesian Rupiah (IDR) or US Dollars (USD). Taxes or external transaction handler processor charges are clearly summarized at checkout.
Because Jepely provides instantly provisioned cloud subscription services, digital data access tokens, and compute resources, **all subscription payments are strictly non-refundable once activated**. Discretionary exceptions are examined only for:
Jepely reserves the full right to audit billing profiles, auto-reject suspicious or unverified transaction layers, and instantly terminate cloud dashboard accounts linked to credit card chargeback attempts or fraudulent data.
For automated plan issues, account upgrades, or transaction reconciliation, route your logs to:
Jepely SaaS Penagihan & Billing
Email: [email protected]
Web: https://jepely.com
Powered by JP Kreasi Infrastructure