anypay

• Minor bug fixing documentations changes

• Minor bug fixing documentations changes

• Minor bug fixing documentations changes

Added

• Official release of AnyPay as a UI-agnostic, adapter-based payments plugin.
• PaymentAdapter interface to integrate any payment provider.
• Unified AnyPay.chargeWithName() API.
• PaymentOptions model for standardized payment input.
• PaymentResult model with explicit payment states: success, failed, pending, error.
• Adapter registration system (AnyPay.registerAdapter).
• Developer-controlled UI for payment states.
• Overlay helper (PaymentStatusOverlay) and animated widget (PaymentStatusWidget) for optional status feedback.
• Improved testing and mocking capabilities.

Changed

• Removed all built-in payment UI, checkout flow, and enforced animations.
• Dependency choice (Stripe, Razorpay, PayPal, etc.) delegated to the developer.
• Core package now focuses entirely on payment abstraction and status reporting.

Breaking Changes

• Built-in payment UI and animations from previous dev versions are no longer included.
• Developers must implement their own UI and animations for success, failed, pending, or error states.

Notes

• This release establishes the foundation architecture for AnyPay v0.1.0.
• Future releases may include optional UI helpers, animated overlays, and official adapters.

---

Added / Changed

• Transitioned from UI-driven design to adapter-based abstraction.
• Documentation updated for the new architecture.
• Internal mock adapters introduced for testing.

Breaking Changes

• All built-in UI and animations removed.

---

Changed

• Work-in-progress refactoring of payment handling towards abstraction.

---

Added

• Experimental UI components and payment state handling.

---

Added

• Initial dev release with built-in UI prototype.
• Checkout and status screens.
• Customizable theme and animations.
• Example app simulating payment outcomes.