Real-World Example
Jane has a scheduled payment due today for ABC Collections. The system should use ABC Collections’ merchant account when charging Jane’s saved payment method. ABC Collections can connect Authorize.net or USAePay for consumer payments. Old Stripe consumer merchant configurations and credentials are removed. A creditor who previously used that configuration must connect a supported processor before consumer payments can run. Stripe used for YouNegotiate membership and usage billing is separate. If ABC Collections has not completed supported merchant setup, the payment should not be treated as ready to process. The creditor should be guided to finish merchant setup before consumer payments can run normally.Visual Flow
How It Should Work
- It should offer only Authorize.net and USAePay for consumer-payment processing.
- Stripe should be absent from processor options, credential forms, and accepted merchant settings.
- Connecting a supported processor should verify its complete credential set before saving.
- The cleanup should remove old Stripe consumer merchant configurations, gateway profiles, payment attempts, credential audits, and the stored Stripe-secret field. Supported processor and platform billing data should remain unchanged.
- Unsupported processors should not count as completed merchant setup or enable consumer payment methods.
- Immediate payments, scheduled payments, and retries should stop before processing through an unsupported processor.
- Payment processing should use the correct merchant account for the creditor and payment method.
- If extra information is required, the creditor should be guided to provide it.
How It Should Not Work
- It should not accept Stripe as a new or updated consumer-payment processor, even when its key is valid.
- It should not retain a compatibility path that treats removed Stripe configurations as usable.
- It should not change Stripe membership or usage billing when changing consumer processor support.
- It should not charge consumers through the wrong merchant account.
- It should not expose sensitive payment credentials to unauthorized users.
- It should not allow payment processing when required merchant setup is incomplete.

