Repository navigation
docs product payments offer policy
Owner: payment plan. Rules: B-BR-PAY-01–24 and BUC-PAY-01–10. Golden cases: offer-policy-v1.json.
This policy freezes the technical offer and paid-through envelope needed by the
payment implementation. It does not approve a commercial price, tax/fiscal
workflow, provider account or live sale. No monetary value in this document is a
production price. The only amount is a clearly synthetic test fixture
(1234 centavos) and must never be shown to a payer or registered at a provider.
All three selected sale channels remain independently disabled:
| Channel | New sales | Maintenance (when implemented) | Current blocker |
|---|---|---|---|
stripe_card |
OFF | required | merchant/Price IDs, webhook, tax/consent review |
asaas_pix_manual |
OFF | required | merchant/API/webhook, catalog, fiscal review |
asaas_pix_automatic |
OFF | required | merchant eligibility, authorization contract, sandbox proof |
Disabling new sales must not disable webhook intake, reconciliation, cancellation, refunds, export or already-earned paid-through access. No secret presence may enable a channel; activation requires the approved catalog and the provider-proof gates in the plan.
Catalog version: pay-catalog-v1. Currency: BRL; money is integer centavos,
never floating point. The server, not the client, selects offer, amount, term,
capabilities and provider mapping.
| Field | Frozen value |
|---|---|
| Offer ID | premium.monthly |
| Product family | premium |
| Payer | one authenticated account |
| Term | one calendar month (P1M), monthly anchor |
| Capabilities |
cloud.sync, cloud.backup, cloud.restore, alerts.advanced, professional.write, professional.report, vehicles.multiple
|
| Channels | card, conventional Pix, Pix Automático (independent) |
| Production amount | UNRESOLVED |
| Test amount |
1234 centavos, synthetic only |
| Sale | DISABLED |
The capability list is the existing verified Premium bundle. Web payments extend the existing subscription/access owner; they do not create a second entitlement or grant free features retroactively. Free status/export/deletion and existing local data remain outside paid checks.
No Enterprise offer is sellable. The only candidate is a single accountable payer for a versioned regional fuel-price brief derived from admitted public data.
| Field | Frozen value |
|---|---|
| Offer ID |
enterprise.regional_brief.v1 (candidate, not sellable) |
| Payer | one accountable legal entity/person |
| Deliverable | periodic regional fuel-price brief; no private portal or API |
| Capabilities | none in the app; no team/seat/station/tenant right |
| Term | UNRESOLVED |
| Production amount | UNRESOLVED |
| Sale | DISABLED |
The candidate remains blocked by: deliverable not implemented, source rights/redistribution pending, demand unvalidated, price/term unresolved and fiscal workflow unresolved. Enterprise payment must never create organization membership, team access, station representation/management, a private portal or cross-account capability. Premium and Enterprise remain independent.
- Exactly one settled payment funds exactly one paid period. A payment may not fund two periods and a period may not be funded twice. A repeated settlement for the same order is excess even when a future-period slot exists.
- At most one future period may be held beyond the current paid-through period.
A second early payment is
EXCESS_UNAPPLIEDand does not extend access. - No trial, coupon, zero-price grant, installment, wallet credit or automatic proration is supported in v1. Requests for them are refused.
- Only the monthly term is supported. Annual or multi-month terms require a new policy version.
- A price/catalog change applies at the next term boundary; already earned paid-through is preserved. A quote carries the catalog version and expires.
- Underpayment, overpayment, wrong currency or a client-supplied amount is refused; it never creates a partial period or a wallet balance.
- Provider prices/plans are mapped by explicit IDs at PAY-02/05. Startup must not create products, prices, customers or webhooks.
Billing civil dates use America/Sao_Paulo; stored instants are UTC. Periods are
half-open [start, end).
- The first period starts at the authoritative settlement instant and ends one calendar month later. The local settlement day becomes the contract anchor.
- Adding a month clamps the anchor to the target month's last day (for example, day 31 becomes February 28/29) while preserving the original anchor for later periods.
-
Early renewal (settlement at or before current
end) starts at currentend, not at payment time. It does not create a gap or overlap. -
Late renewal (settlement after current
end) starts at the settlement instant and resets the anchor to that local day. It grants no retroactive access. - Grace is 0 seconds in v1. At
end, access is no longer active; card retries or a provider past-due state do not extend local access. - Cancellation stops future renewal. It does not erase the paid-through period, automatically refund, delete data or disable free export.
- Access also requires the existing live account proof and a verified settlement. A redirect, QR creation, authorization, invoice creation or unknown provider state grants nothing.
Exact examples are in the golden fixture. The first and last examples:
| Case | Start | End |
|---|---|---|
| Initial settlement on 2026-01-31 | 2026-01-31T12:00:00Z |
2026-02-28T12:00:00Z |
| Leap-year settlement on 2028-01-31 | 2028-01-31T12:00:00Z |
2028-02-29T12:00:00Z |
| Early renewal while paid through 2026-02-28 | 2026-02-28T12:00:00Z |
2026-03-31T12:00:00Z |
| Late renewal after 2026-03-31, paid 2026-04-02 | 2026-04-02T12:00:00Z |
2026-05-02T12:00:00Z |
- Refunds are supported only to the original provider payment route, bounded by the original gross amount. A refund request/loss is not a completed refund.
- A partial refund is a financial adjustment and does not shorten access.
- A cumulative full refund or confirmed chargeback/reversal of the payment that funded a period revokes the unexpired remainder of that period at the confirmation instant. Already elapsed time is not re-granted.
- A pending dispute is not a confirmed fraud finding and does not by itself revoke access. A confirmed chargeback applies only to its matched payment/period.
- An account-level provider hold without a matched payment does not revoke every payer; it is surfaced for review.
- A duplicate or excess settlement is recorded as
EXCESS_UNAPPLIED, never as extra access or an automatic wallet credit. Its refund is handled by PAY-16. - Cancellation and account deletion never create an automatic refund.
One product family has at most one recurring funding source per account.
- Plan/term switching takes effect at the next term boundary. No implicit proration; immediate upgrades/proration remain unsupported.
- The old recurring source must be canceled/fenced with a confirmed provider outcome before a new automatic source may debit. An unknown cancellation blocks the new automatic activation.
- Card ↔ Pix Automático: cancel the old renewal, confirm it, activate the new source for the next term, and preserve the current paid-through period.
- Pix Automático → card: do not create a card renewal before the old mandate is confirmed stopped.
- Manual Pix → card or Pix Automático: the manual paid period remains valid until its end; the recurring source may activate for the next term only. A manual payment is not recurring consent.
- Concurrent manual Pix and automatic settlement may produce excess money; it produces at most one paid period. Excess follows the refund/excess policy.
Conventional Pix and Pix Automático are different products with independent switches:
- Conventional Pix creates one owner-bound charge/QR per order. It has no implicit recurring consent. Only an authoritative receipt funds its period.
- Pix Automático requires an admitted merchant, explicit payer authorization, and a mandate. The initial payment and the mandate are independent: a refused authorization can coexist with a paid first period, but no future debit is allowed until authorization is ACTIVE.
- The selected cycle owner is Asaas provider-owned SUBSCRIPTION. The application does not run a second cycle scheduler. If PAY-02 cannot admit the provider-owned contract for the required terms, Pix Automático remains disabled; switching to application-owned MANUAL requires a new recorded decision, not a silent fallback.
- Recurring consent must state price, term, renewal cadence, cancellation and support contact before checkout. Final Portuguese wording and legal review are PENDING; the channel stays off until approved.
- A provider invoice/receipt is not a Brazilian fiscal document. Fiscal issuer, tax treatment, invoice handling and retention are UNRESOLVED. No tax engine is built in this scope.
- CPF/CNPJ, billing address and contact data are minimized; no CPF/CNPJ is required merely to create a free account. Retention/erasure of financial metadata requires the privacy review at PAY-15/20.
- Provider email/SMS/WhatsApp notifications are OFF/UNDECIDED to avoid duplicate or unapproved messages. Application notification delivery is configured separately.
- Android purchase UI, store links or steering are DISABLED until the applicable Play distribution/policy decision is verified. Web backend work does not authorize an in-app purchase flow.
Stripe Price IDs, Asaas product/plan IDs, merchant/account IDs, webhook endpoints, API/SDK versions, allowed return origins and test/live separation are not defined by this policy. They are admitted at PAY-02/05 and proven at PAY-21. No API key alone closes these gates.
offer-policy-v1.json contains synthetic, versioned cases for: month-end/leap anchors, early and late renewal, zero grace boundaries, partial/cumulative/full refunds, pending dispute vs confirmed chargeback, duplicate/excess settlement, amount mismatch, method switching with confirmed/unknown cancellation, and disabled Premium/Enterprise/ trial/annual/Android sale paths.
PAY-03 must implement these deterministic rules behind provider-neutral ports. PAY-06/07/10/11/12/13/14/16 must consume them. A case is accepted only when the actual implementation test passes; this document and fixture are not runtime evidence.
- Approved public Premium price, term and any trial decision.
- Approved Enterprise deliverable/capabilities and price, plus source rights, demand evidence and a permitted delivery model.
- Tax/fiscal issuer and retention decision; approved recurring consent text.
- Provider merchant/account approval, catalog IDs, webhook setup and test/live separation.
- Pix Automático eligibility and actual provider cycle contract.
- Distribution decision for any Android purchase surface.
Until all applicable inputs and the phase-specific provider proofs exist, the
catalog remains PRODUCTION_SALES_DISABLED.
- Home
- Roadmap
- docs-README
- docs-android-build
- docs-android-design-system
- docs-android-forum
- docs-android-games
- docs-android-map-engine
- docs-android-navigation
- docs-android-ocr-image
- docs-android-ocr-live-framing
- docs-android-premium-area
- docs-android-premium-integration
- docs-android-release
- docs-android-ui-containers
- docs-architecture-android-stack
- docs-architecture-android
- docs-architecture-backend
- docs-architecture-data-sources
- docs-architecture-overview
- docs-architecture-sources-ev-research
- docs-architecture-sources-national-limits
- docs-architecture-sources-national-stations
- docs-architecture-sources-register
- docs-assets-app-tutorial-CAPTURE_CONTRACT
- docs-assets-app-tutorial-FABLE_LANDING_POLISH_PROMPT
- docs-assets-app-tutorial-README
- docs-assets-attribution
- docs-assets-brand-README
- docs-assets-flags-ATTRIBUTION
- docs-assets-fuel-icons-README
- docs-assets-games-fuel-v1-README
- docs-assets-home-icons-README
- docs-assets-landing-fleet-android-20261012-BRIEF
- docs-assets-landing-hero-20261011-BRIEF
- docs-assets-landing-illustrated-20261012-BRIEF
- docs-assets-landing-illustrated-20261012-README
- docs-assets-landing-minimal-20261012-BRIEF
- docs-assets-landing-open-data-20261026-BRIEF
- docs-assets-landing-redesign-20261011-PREPARATION_EVIDENCE
- docs-assets-landing-redesign-20261011-README
- docs-assets-landing-redesign-20261011-REFERENCE_BRIEF
- docs-assets-landing-sync-20261012-BRIEF
- docs-assets-map-icons-README
- docs-backend-anp-ingestion
- docs-backend-api
- docs-backend-community-pricing
- docs-backend-data-model
- docs-backend-domain-model
- docs-backend-driver-private-data
- docs-backend-forum-architecture
- docs-backend-forum-bulletins
- docs-backend-forum-sources
- docs-backend-payments-provider-admission
- docs-backend-payments-provider-register
- docs-backend-photos-capture
- docs-backend-photos-subset-submission
- docs-backend-premium-api
- docs-backend-premium-cloud-protocol
- docs-backend-testing
- docs-backend-toolchain
- docs-brand-app-icons
- docs-brand-identity
- docs-decisions-001-kotlin-compose-stack
- docs-decisions-002-price-import-immutability
- docs-decisions-003-nominatim-reverse-geocode
- docs-decisions-005-modular-monolith-and-postgresql
- docs-decisions-006-official-catalog-and-exact-contracts
- docs-decisions-007-anonymous-proof-of-possession
- docs-decisions-008-privacy-and-retention
- docs-decisions-009-community-consensus-and-projections
- docs-decisions-010-private-object-evidence
- docs-decisions-012-licensing-and-hosted-business
- docs-decisions-015-kotlin-multiplatform-shared-domain
- docs-decisions-016-android-commercial-community-ios-deferred
- docs-decisions-017-station-profile-and-verified-representation
- docs-decisions-021-community-first-contribution
- docs-decisions-022-comaps-derived-native-map-engine
- docs-decisions-023-admin-suite-granted-tiers-contributors
- docs-decisions-025-private-abastevo-empresas-organization-boundary
- docs-decisions-026-multilingual-public-site
- docs-decisions-README
- docs-enterprise-README
- docs-enterprise-architecture
- docs-enterprise-backlog-INDEX
- docs-enterprise-backlog-ep00-governance
- docs-enterprise-backlog-ep01-platform
- docs-enterprise-backlog-ep02-organizations
- docs-enterprise-backlog-ep03-identity-access
- docs-enterprise-backlog-ep04-sync
- docs-enterprise-backlog-ep05-fleet-meters
- docs-enterprise-backlog-ep06-trips
- docs-enterprise-backlog-ep07-gps-navigation
- docs-enterprise-backlog-ep08-fuelings
- docs-enterprise-backlog-ep09-documents
- docs-enterprise-backlog-ep10-expenses-finance
- docs-enterprise-backlog-ep11-maintenance
- docs-enterprise-backlog-ep12-fuel-stock
- docs-enterprise-backlog-ep13-intelligence
- docs-enterprise-backlog-ep14-station-claims
- docs-enterprise-backlog-ep15-station-commerce
- docs-enterprise-backlog-ep16-subscriptions
- docs-enterprise-backlog-ep17-data
- docs-enterprise-backlog-ep18-imports-notifications-integrations
- docs-enterprise-backlog-ep19-back-office
- docs-enterprise-backlog-ep20-release
- docs-enterprise-business-rules
- docs-enterprise-contract
- docs-enterprise-conventions
- docs-enterprise-data-offering
- docs-enterprise-decisions
- docs-enterprise-domain-model
- docs-enterprise-glossary
- docs-enterprise-journeys
- docs-enterprise-modules-back-office
- docs-enterprise-modules-data
- docs-enterprise-modules-documents
- docs-enterprise-modules-expenses-finance
- docs-enterprise-modules-fleet
- docs-enterprise-modules-fuel-stock
- docs-enterprise-modules-fuelings
- docs-enterprise-modules-gps-navigation
- docs-enterprise-modules-identity
- docs-enterprise-modules-imports-notifications-integrations
- docs-enterprise-modules-intelligence
- docs-enterprise-modules-maintenance
- docs-enterprise-modules-organizations
- docs-enterprise-modules-station-claims
- docs-enterprise-modules-station-commerce
- docs-enterprise-modules-subscriptions
- docs-enterprise-modules-trips
- docs-enterprise-offline-sync
- docs-enterprise-permissions
- docs-enterprise-portal-routes
- docs-enterprise-privacy-security
- docs-enterprise-product-vision
- docs-enterprise-source-admission
- docs-enterprise-state-model
- docs-enterprise-testing
- docs-enterprise-ux-app
- docs-enterprise-ux-web
- docs-operations-README
- docs-operations-backup
- docs-operations-deploy-agent
- docs-operations-dou-editions
- docs-operations-edge-cache
- docs-operations-enterprise-activation
- docs-operations-map-static-overlay
- docs-operations-moderation-feedback
- docs-operations-moderation-profiles
- docs-operations-monitoring
- docs-operations-operator-access
- docs-operations-payments
- docs-operations-premium-billing
- docs-operations-recovery
- docs-operations-registry-daily-sync
- docs-operations-registry-runs
- docs-product-README
- docs-product-admin-tiers
- docs-product-community-community-first
- docs-product-community-experience
- docs-product-community-metrics
- docs-product-community-moderation
- docs-product-community-safety
- docs-product-community-terms-pt-br
- docs-product-driver-suite-README
- docs-product-driver-suite-android-state
- docs-product-driver-suite-cloud-sync
- docs-product-driver-suite-cost-profiles-and-maintenance
- docs-product-driver-suite-driver-model-and-earnings
- docs-product-driver-suite-foundation-decisions
- docs-product-driver-suite-gps-lifecycle
- docs-product-driver-suite-mobile-hub
- docs-product-driver-suite-odometer-review
- docs-product-driver-suite-outbox-wire
- docs-product-driver-suite-quick-refuel
- docs-product-driver-suite-reports
- docs-product-driver-suite-shifts-and-distance
- docs-product-driver-suite-signed-commands
- docs-product-ev-README
- docs-product-ev-charging-stop-planner
- docs-product-ev-energy-model
- docs-product-ev-financial-method
- docs-product-ev-journey-ui
- docs-product-ev-preparation
- docs-product-ev-typed-data
- docs-product-exploration
- docs-product-forum-contract
- docs-product-forum-policies
- docs-product-glossary
- docs-product-landing-content
- docs-product-landing-guides
- docs-product-landing-organic-growth-i18n-plan
- docs-product-licensing
- docs-product-map-discovery
- docs-product-map-favorites-and-trips
- docs-product-map-reports-routing-guidance
- docs-product-notification-content
- docs-product-official-prices
- docs-product-open-source-business
- docs-product-overview
- docs-product-payments-README
- docs-product-payments-offer-policy
- docs-product-premium-README
- docs-product-premium-financial-method
- docs-product-premium-source-policy
- docs-product-stations-catalog
- docs-product-stations-fuel-feedback
- docs-product-stations-fuel-quality
- docs-product-stations-identity-and-ev-catalog
- docs-product-stations-profile-contract
- docs-product-stations-profile-representation
- docs-product-stations-registry-sources
- docs-product-vehicle-registration
- docs-product-vehicles-and-occurrences
- docs-security-android-terms-acceptance
- docs-security-free-account-access
- docs-security-identity-profile
- docs-security-media-location-policy
- docs-security-privacy-notice
- docs-security-privacy-policy
- docs-security-retention
- docs-security-risks
- docs-security-security-privacy
- docs-store-README
- docs-store-play-readiness
- docs-store-play-store-listing
- docs-store-ugc-safety
Source: AlexandreZanata/Abastevo @ e4a67580fc368a59bc1c0f1e0466fc011313f330