TransactKit-Pro testing

Browser API console

Run the project and open http://localhost:8080/api-test/index.html. The same-origin console exposes 22 actions, keeps returned identifiers in page memory for follow-up requests, and displays request status and response JSON.

Postman workflow

Import TransactKit-Pro-API.postman_collection.json from the source root. The collection covers the shipped API surface and stores example identifiers, but no Stripe credentials.

Offline automated verification

The standard suite requires no Stripe key, Stripe CLI, MySQL, browser, or internet service. It covers validation and error mapping, H2/Flyway/JPA, Customer and catalogue mapping, Checkout identity and retries, refunds, subscription lifecycle, Portal, invoices, Entitlements, Meter Events, webhook signatures, durable retries, and ownership recovery rules.

./mvnw clean verify

.\mvnw.cmd clean verify

Optional stripe-mock contract profile

Start the official stripe-mock separately on http://localhost:12111 before using this opt-in profile. It validates official SDK request serialization, route names, and response mapping through the real Controller -> Service -> StripeClient path.

./mvnw -Pstripe-mock clean verify

Stripe sandbox and deployment acceptance

• Test real hosted Checkout and Portal navigation.
• Exercise declines, 3DS, refunds, renewals, failed payments, trials, plan changes, cancellation, invoices, Entitlements, Meter Events, Tax, and webhook ordering.
• Run Flyway migrations against a production-like MySQL environment.
• Verify host authentication, ownership checks, authorization, rate limits, audit policy, logging, monitoring, backups, and restore behavior.