# QA Checklist (/online/getting-started/checklist)



Run through this checklist against the [sandbox environment](./testing), then complete the production checks before accepting live payments. It
covers payment outcomes, verification, retries, configuration, and security. Tick each check as you verify it.

<ChecklistProgress />

## 1. Payment outcomes [#1-payment-outcomes]

<ChecklistItem id="OP-PO-1" code="PO-1" title="Successful payment">
  Pay with 

  `4242 4242 4242 4242`

  . The retrieved session has 

  `paymentStatus: successful`

   and the order is fulfilled once.
</ChecklistItem>

<ChecklistItem id="OP-PO-2" code="PO-2" title="Declined card">
  Pay with 

  `4916 0184 7581 4056`

  . The order stays unpaid, and a retry with the success card works while the session is open.
</ChecklistItem>

<ChecklistItem id="OP-PO-3" code="PO-3" title="3D Secure">
  Pay with 

  `4012 0018 0000 0016`

   and complete the challenge. Fulfillment waits for the retrieved status.
</ChecklistItem>

<ChecklistItem id="OP-PO-4" code="PO-4" title="Processing error">
  Use a processing-error test card for the test gateway. The order stays unpaid even though the card form accepted the card.
</ChecklistItem>

<ChecklistItem id="OP-PO-5" code="PO-5" title="Unhandled states">
  Your code treats 

  `unpaid`

  , 

  `failed`

  , 

  `action_needed`

  , 

  `cancelled`

  , and unknown values as not paid. See 

  [Payment status](/online/integration/api_integration#payment-status)

  .
</ChecklistItem>

## 2. Verification and fulfillment [#2-verification-and-fulfillment]

<ChecklistItem id="OP-VF-1" code="VF-1" title="Server-side check">
  Fulfillment compares order reference, amount, currency, and 

  `paymentStatus`

   with the stored order, not the redirect.
</ChecklistItem>

<ChecklistItem id="OP-VF-2" code="VF-2" title="Unpaid success URL">
  Visit the success URL directly without paying. The order stays unpaid.
</ChecklistItem>

<ChecklistItem id="OP-VF-3" code="VF-3" title="Cancel link">
  Follow Checkout's cancel link. The order stays unpaid, and your code does not assume a 

  `cancelled`

   status from the navigation alone.
</ChecklistItem>

<ChecklistItem id="OP-VF-4" code="VF-4" title="Repeated return">
  After a successful payment, reload the return page twice. The order is fulfilled once.
</ChecklistItem>

## 3. Retries and interruptions [#3-retries-and-interruptions]

Use a fresh test order and session for each independent case. For retry tests, reuse the original order, request body, and idempotency key.

<ChecklistItem id="OP-RI-1" code="RI-1" title="Lost create response">
  Discard the create response in your test harness and repeat with the same 

  `Idempotency-Key`

   and body. The original session is replayed and no second one is created.
</ChecklistItem>

<ChecklistItem id="OP-RI-2" code="RI-2" title="Changed body">
  Reuse a key with a different body. The API returns HTTP 409 and your code does not treat it as a new session.
</ChecklistItem>

<ChecklistItem id="OP-RI-3" code="RI-3" title="Customer never returns">
  Pay, then close the tab before it returns. Your reconciliation job retrieves the stored session and records the payment once.
</ChecklistItem>

<ChecklistItem id="OP-RI-4" code="RI-4" title="Status timeout">
  Make retrieval time out. Your app keeps the session ID, leaves the outcome unresolved, and does not create a replacement session.
</ChecklistItem>

<ChecklistItem id="OP-RI-6" code="RI-6" title="Replaced session">
  Create a second session for the same unpaid order. The first URL reports 

  `expired`

   and cannot take payment. After the order is paid, creating another session returns HTTP 409.
</ChecklistItem>

<ChecklistItem id="OP-RI-5" code="RI-5" title="Session expiry">
  Wait past 

  `expiresAt`

   (30 minutes) and reopen the URL. No new payment can start and the order stays unpaid.
</ChecklistItem>

## 4. Checkout settings [#4-checkout-settings]

<ChecklistItem id="OP-CS-1" code="CS-1" title="Merchant approved">
  Each merchant you take payments for is in the 

  **Checkout merchants**

   table with status 

  **Ready**

  .
</ChecklistItem>

<ChecklistItem id="OP-CS-2" code="CS-2" title="Return destinations">
  Default success and cancel URLs are set for the credential you use (organization defaults for the Secret key, the merchant's settings for a merchant key), use HTTPS, and their exact origins are in that credential's 

  **Allowed websites**

  .
</ChecklistItem>

<ChecklistItem id="OP-CS-3" code="CS-3" title="Per-session overrides">
  Any 

  `successUrl`

   or 

  `cancelUrl`

   you send matches a configured origin.
</ChecklistItem>

<ChecklistItem id="OP-CS-4" code="CS-4" title="Wallets">
  Apple Pay and Google Pay are on or off as intended. Live Google Pay has a Google Pay merchant ID configured.
</ChecklistItem>

<ChecklistItem id="OP-CS-6" code="CS-6" title="Embedded wallets">
  The wallet total matches the server order. Changing shipping or discounts updates it. Wallet cancellation leaves checkout available, and pending payments block another charge.
</ChecklistItem>

<ChecklistItem id="OP-CS-5" code="CS-5" title="Branding">
  Color and logo look right in 

  **Checkout preview**

   on both desktop and mobile layouts.
</ChecklistItem>

## 5. Security [#5-security]

<ChecklistItem id="OP-SE-1" code="SE-1" title="Key on the server">
  Your merchant checkout key or organization Secret key is only in server configuration, never in browser code, app bundles, or source control.
</ChecklistItem>

<ChecklistItem id="OP-SE-2" code="SE-2" title="Server-owned totals">
  Amount, currency, and order ID come from your stored order, never from the browser.
</ChecklistItem>

<ChecklistItem id="OP-SE-3" code="SE-3" title="Embedded endpoints">
  If you use embedded payments, 

  `prepare`

   and 

  `submit`

   are bound to an authenticated checkout or signed HTTP-only cookie, and mutation origins are validated.
</ChecklistItem>

<ChecklistItem id="OP-SE-4" code="SE-4" title="Content security policy">
  If you use embedded payments, your CSP allows Tapaya's script and frame origins, and 3D Secure challenges still work under it.
</ChecklistItem>

## 6. Sandbox configuration [#6-sandbox-configuration]

<ChecklistItem id="OP-PR-1" code="PR-1" title="Sandbox API">
  `TAPAYA_CHECKOUT_API_URL`

   points at 

  `https://api.sandbox.tapaya.com`

  .
</ChecklistItem>

<ChecklistItem id="OP-PR-2" code="PR-2" title="Sandbox key">
  The integration uses a sandbox merchant checkout key or organization Secret key, loaded from server configuration.
</ChecklistItem>

<ChecklistItem id="OP-PR-3" code="PR-3" title="Reconciliation job">
  The job that retrieves unresolved sessions is scheduled in your test environment.
</ChecklistItem>

## 7. Production readiness [#7-production-readiness]

<ChecklistItem id="OP-LV-1" code="LV-1" title="Merchant readiness">
  The live merchant completed onboarding with online payments, received processor approval, and has a configured payment gateway. The merchant is 

  **Ready**

   in Checkout settings.
</ChecklistItem>

<ChecklistItem id="OP-LV-2" code="LV-2" title="Live credentials">
  The server uses production credentials and 

  `https://api.tapaya.com`

  . SDK integrations set 

  `TAPAYA_ENVIRONMENT=production`

  . Sandbox keys and test cards are not used for live payments.
</ChecklistItem>

<ChecklistItem id="OP-LV-3" code="LV-3" title="Live wallets">
  Apple Pay shop domains are active. Live Google Pay has a configured merchant ID. Supported wallets complete a payment and recover after cancellation.
</ChecklistItem>

<ChecklistItem id="OP-LV-4" code="LV-4" title="Live reconciliation">
  Production return URLs, server verification, fulfillment, and the reconciliation job use production configuration.
</ChecklistItem>

## 8. Saved methods and delivery [#8-saved-methods-and-delivery]

Run the checks for the features your integration uses.

<ChecklistItem id="OP-SD-1" code="SD-1" title="Saving consent">
  Optional saving starts unchecked. Required saving follows consent collected by your checkout. A changed policy requires review, and a successful payment is never charged again because saving is delayed.
</ChecklistItem>

<ChecklistItem id="OP-SD-2" code="SD-2" title="Saved-card verification">
  Customer-initiated verification can complete, close, and retry with the same payment. The hosted fallback returns to an allowed URL. Your server verifies the outcome before fulfillment.
</ChecklistItem>

<ChecklistItem id="OP-SD-3" code="SD-3" title="Merchant-initiated charges">
  Only the authenticated customer's eligible off-session method can be charged. A decline or pending result is not reported as success. Replaying an operation key creates no duplicate charge.
</ChecklistItem>

<ChecklistItem id="OP-SD-4" code="SD-4" title="Authorization lifecycle">
  Manual capture holds funds until capture or release. Partial capture releases the remainder. Expired holds cannot be captured, and pending operations block conflicting actions.
</ChecklistItem>

<ChecklistItem id="OP-SD-5" code="SD-5" title="Zero-amount setup">
  Zero requires required saving and no shipping. Verify a card and supported wallets, wait for the saved method ID, and confirm that no purchase is fulfilled.
</ChecklistItem>

<ChecklistItem id="OP-SD-6" code="SD-6" title="Customer collection">
  Hosted session creation rejects missing contacts when neither 

  `customer.email`

   nor 

  `customer.phone`

   is supplied. Embedded confirmation rejects missing contacts. Required name and billing fields block incomplete submission; optional fields can be skipped. Accepted details appear on server reads.
</ChecklistItem>

<ChecklistItem id="OP-SD-7" code="SD-7" title="Shipping approval">
  Fixed and dynamic options use full final amounts. Stale revisions, expired quotes, and unsupported destinations cannot charge. Changed totals require review, and fulfillment compares the server-approved final amount.
</ChecklistItem>

<ChecklistItem id="OP-SD-8" code="SD-8" title="Hosted callback">
  A valid raw-body signature passes. Changed bodies or signatures fail before pricing. The callback answers within five seconds, and its secret never reaches the browser.
</ChecklistItem>

<ChecklistItem id="OP-SD-9" code="SD-9" title="Wallets on devices">
  Test shipping callbacks, contact collection, off-session agreements, cancellation, and zero-amount setup on real supported Apple Pay and Google Pay devices.
</ChecklistItem>

<ChecklistItem id="OP-SD-10" code="SD-10" title="Refund reconciliation">
  A partial or full refund uses a stored operation key. Replays do not duplicate it, and only a retrieved succeeded refund is treated as returned funds.
</ChecklistItem>

<ChecklistProgress />

<Callout title="Sign-off" type="tip">
  Complete the sandbox tests and production readiness checks. Use **Reset** to start a clean run, since ticks from earlier test rounds stay saved in this browser.
</Callout>
