Payments QA Runbook

Use this runbook in Vesper QA only:

https://exodus--vesper.sandbox.lightning.force.com

QA Scope

Validate the full payment path when payment metadata, settings, gateway routing, quote readiness, checkout, recurring plans, settlement, or payment reports change.

Preconditions

Gateway Readiness

1. Open Payment Gateway Connections.
2. Confirm Sandbox A and Sandbox B are active and not production gateways.
3. Run/inspect connection checks if gateway code changed.
4. Confirm lifecycle status is correct.
5. Confirm no production gateway is mixed into the test route.

If a gateway is deprecated or removed, use the successor-backed lifecycle docs before testing customer payment.

Saved Method Flow

1. Open a QA Account or Contact.
2. Use Add_Payment_Method.
3. Enter the sandbox test card.
4. Save it to the customer vault.
5. Confirm the payment vault/inventory view shows token coverage for the expected routes.
6. Confirm the card appears once with gateway token chips rather than duplicate saved methods.

Expected result: saved card ending in 4242 is visible and route readiness messages are accurate.

Quote and Sales Order Flow

1. Create or use a QA quote with payment-required conditions.
2. Confirm quote payment readiness.
3. Submit for approval.
4. Approve through the supported review action.
5. Convert or sync to Sales Order.
6. Open the Sales Order payment console.
7. Confirm saved method and route-level token selectors.

If readiness says retokenization required, do not override it. Diagnose gateway/token coverage.

Payment Link Checkout

1. Create a Payment Order from Sales Order or use an existing QA Payment Order.
2. Send a payment link email from Salesforce.
3. Open the payment link in the QA/browser replay context.
4. Pay with the sandbox test card.
5. Confirm Payment Intent, Attempt, Transaction, Receipt, Allocation, and Invoice/Sales Order state.
6. Confirm the email/action history is recorded.

Do not use a manually built checkout URL.

Recurring Plan QA

1. Confirm Payment Operations Settings allow recurring payments for the test.
2. Create or manage a recurring plan from Sales Order.
3. Confirm Payment_Agreement__c state, next scheduled payment, amount, method, and route.
4. Test pause, resume, and cancel actions.
5. Confirm agreement PDF generation when relevant.

Scheduler installation and settings toggles are separate checks. A class existing in metadata does not mean live automation is enabled.

Refund, Void, and Dispute QA

Use sandbox data only.

Settlement and Reporting

After payment execution:

1. Review Payment Operations Dashboard.
2. Review AR/payment reports.
3. Confirm gateway accounting reports include the transaction.
4. Confirm settlement sync fields or settlement records if settlement behavior changed.
5. Confirm Metric Integrity Dashboard has no new payment issues.

Exit Criteria

Payments QA is complete when:

1. Gateway readiness is confirmed.
2. Saved method and token coverage behave as expected.
3. Payment link checkout creates the expected payment evidence.
4. Sales Order/Invoice/AR state updates correctly.
5. Recurring/refund/dispute paths are tested if changed.
6. Reports and dashboards reflect the result.
7. All test data is labeled or included in the run evidence.