v0.4.1

What's Changed

• Add Authorize.Net to the architecture and operations guides by @MHJaafar9869 in #31
• Add AI & MCP documentation suite (100% package coverage) by @MHJaafar9869 in #32
• Link the AI docs under the Misc tab of the interactive docs by @MHJaafar9869 in #33
• Add Authorize.Net tokenization (Customer Information Manager) by @MHJaafar9869 in #34

Full Changelog: v0.4.0...v0.4.1

v0.4.0

What's Changed

• Add Authorize.Net gateway by @MHJaafar9869 in #30

Full Changelog: v0.3.3...v0.4.0

v0.3.3

What's Changed

• Send 3-D Secure browser device data on the MPGS authenticate call by @MHJaafar9869 in #26
• Show the current package version (v0.3.2) in the docs by @MHJaafar9869 in #27
• Add a Markdown-driven changelog page to the docs by @MHJaafar9869 in #28
• Refactor Paymob checkout into a Laravel pipeline by @MHJaafar9869 in #29

Full Changelog: v0.3.2...v0.3.3

v0.3.2

CyberSource Decision Manager device fingerprinting — completed across all payment flows.

Manual (transient-token) flow

• deviceInformation.fingerprintSessionId now carried on stored-credential (MIT/CIT) charges and 3DS payer-auth enrollment (it was already sent on charge).
• New latest-REST useRawFingerprintSessionId flag on ChargeRequest, StoredCredentialChargeRequest, and PayerAuthEnrollRequest (default false), via a shared DeviceInformation payload helper.

Orchestrated (completeMandate) flow

• New decisionManager flag on CheckoutSessionRequest (default true), emitted as completeMandate.decisionManager so orchestrated Unified Checkout payments run Decision Manager (device fingerprinting included) by default.

Docs

• New "Device fingerprinting (Decision Manager)" section in docs/guides/operations.md and the interactive docs/guide.html, including the browser tags.js profiling tag, standard org ids (1snn5n9w test / k8vif92e production), and the orchestrated decisionManager path.

All constructor additions are appended, preserving positional-argument backward compatibility. Quality gate green (Pint, Rector, PHPStan level max, 280 Pest tests).

Full changelog: v0.3.1...v0.3.2

v0.3.1

Full Changelog: v0.3.0...v0.3.1

v0.3.0

What's Changed

• Add CyberSource Unified Checkout orchestrated flow (completeMandate + result-JWT verification) by @MHJaafar9869 in #23

Full Changelog: v0.2.0...v0.3.0

v0.2.0

What's Changed

• Document credential resolver and HTTP client ports in docs guide by @MHJaafar9869 in #15
• Flip docs guide side panels: gateway selector left, action list right by @MHJaafar9869 in #16
• Docs guide polish: drop hero + progress bar, Instrument Sans display font by @MHJaafar9869 in #17
• Document CyberSource checkout client library and integrity fields by @MHJaafar9869 in #18
• Genericize docs guide action intros to the selected gateway by @MHJaafar9869 in #19
• Add Mastercard Payment Gateway Services (MPGS) gateway by @MHJaafar9869 in #20
• Add PayLink card tokenization (store, charge, revoke) by @MHJaafar9869 in #21
• Add PayLink chargeStoredCredential (stored-credential token charge) by @MHJaafar9869 in #22

Full Changelog: v0.1.1...v0.2.0

v0.1.1

Patch release.

Fixes

• PayLink checkout returned an empty URL. GetPayIn (PayLink) wraps successful responses in a { "data": { ... }, "success": true } envelope; PaylinkClient now unwraps it, so createCheckoutSession (and all PayLink operations) read the real checkout_url / invoice_id.

Includes docs, README badges, and CI workflow refinements since v0.1.0.

v0.1.0

Self-contained, framework-agnostic multi-gateway payment SDK for PHP 8.2+ (with Laravel auto-discovery).

Gateways / drivers

• CyberSource Unified Checkout
• Fawry
• Paymob
• PayLink
• PayTabs
• PayPal

Highlights

• Unified driver interface for checkout, charge/capture, refund/void/reverse, 3-D Secure, vaulting, transaction lookup, and webhook verification
• HMAC request-signing and webhook signature verification per gateway
• Payment domain events + optional operation logging
• Works standalone or via the Laravel service provider

Fixes

• PayLink checkout returned an empty URL. GetPayIn (PayLink) wraps successful responses in a { "data": { ... }, "success": true } envelope, but the driver read checkout_url / invoice_id at the top level and got null — so createCheckoutSession produced no redirect URL. PaylinkClient now unwraps the data envelope, so checkout returns the hosted URL and every PayLink operation (charge, refund, void, reverse, status) reads the correct fields.

See the documentation to get started.