Payment and Payout Policy

This policy explains the operational rules for payment sessions, developer earnings, refunds, disputes, and payouts on Easyparser App Store. It applies together with the App Store Terms of Service and App Publisher Terms.

It is a product policy, not tax, accounting, legal, or financial advice. Developers remain responsible for their own obligations and should obtain advice appropriate to their situation.

Your backend creates a payment session with an App Store API key. The customer completes payment through an Easyparser-hosted Stripe Checkout session, then returns to the URL configured for that app and environment. Signed webhooks, not the browser redirect alone, are the server-side signal for payment status.

Payment sessions must not be created from browser code or with an exposed API key. TEST and LIVE environments are separate. TEST activity does not create real earnings or payouts.

An app can create a payment session only when its payment activation is approved, it has an approved live version, and its payment configuration is complete for the relevant environment. Easyparser may apply additional activation, risk, or compliance checks before or during use of payment services.

Easyparser collects customer payments through the platform payment account. The default App Store commission is 25% of the payment amount excluding applicable tax, so the normal developer share is 75%. An app can have a different configured commission rate.

Under normal conditions, the developer-facing share does not include the Stripe processing fee. Taxes, refunds, chargebacks, fraud review, and other transaction outcomes can change the recognized earning or the amount available for payout.

A successful LIVE payment creates an earning that is held for 15 calendar days before it can become ready to withdraw. A developer may request a payout only after required identity verification and bank-account verification are complete and the available balance meets the current $25 minimum payout threshold.

Payouts are requested by the developer, reviewed in the platform workflow, and processed through the available payout process. They are not automatic and do not follow a guaranteed fixed schedule. Individual and business payout profiles may be supported, subject to verification and country or banking availability.

A refund, dispute, chargeback, failed payment, or other negative transaction outcome can reduce or reverse a related earning. Where an amount was already paid out, the resulting adjustment may be netted from future eligible earnings or a later payout request.

Customer payment disputes are handled through the payment provider's process. Easyparser may hold, delay, or adjust earnings while it investigates a payment, refund, dispute, fraud signal, or compliance concern.

Keep your return URL, webhook URL, API key, app information, payment configuration, recipient details, and bank account details secure and up to date. Configure your product so that a signed webhook can safely determine access or fulfillment after a payment event.

You must not use the payment integration to evade platform payments, process prohibited transactions, misrepresent a charge, collect card data yourself through the hosted flow, or create fraudulent activity. You must cooperate reasonably with payment, identity, and compliance checks.

We may update this policy to reflect product, payment-provider, security, compliance, or legal requirements. The date above identifies the current version. For questions about payment activation, payout readiness, or an App Store transaction, contact [email protected].