# Testing your Integration

The Finix Payment Sheet Android SDK does not expose a way to verify the integration from the Finix Dashboard - the Dashboard only sees API traffic, which comes from your backend after it receives a token from the SDK. To prove the full flow works, exercise it with a sandbox test card and inspect what each step produces.

## Sandbox prerequisites

- [PaymentSheetConfiguration](/android/online/configuration) using `PaymentSheetEnvironment.SANDBOX` and your Sandbox Application ID.
- A sandbox test card from Finix's [Testing Your Integration](/additional-resources/developers/implementation-and-testing/testing-your-integration) reference.
- For [3D Secure](/android/online/integration#9-enable-3d-secure-optional) flows: Sandbox API credentials and a Merchant ID attached to the same application.


## What to verify

Each link below jumps to the corresponding step in the [Integration Guide](/android/online/integration).

### Tokenization (SDK-only)

1. Launch your app and present the payment sheet - see [Step 4](/android/online/integration#4-present-the-payment-sheet).
2. Enter a sandbox test card and submit.
3. Confirm your `onSuccess` callback fires with a non-null `response.tokenizedResponse.id` - see [Step 5](/android/online/integration#5-get-the-token). A token ID starting with `TK...` means the SDK reached Finix and tokenized the card successfully.
4. Confirm `onFailure` fires (and `onSuccess` does not) when you submit a decline card number.


### Backend handoff

1. Forward the token ID to your backend as you would in production.
2. Create a [Payment Instrument](/android/online/integration#7-create-a-payment-instrument-with-finix) from your backend using the token. A successful response returns a Payment Instrument with `id` starting `PI...` and `instrument_type` matching the card (`PAYMENT_CARD`).
3. Create a [Transfer or Authorization](/android/online/integration#8-process-a-payment) against the Payment Instrument. A successful response returns an object in `SUCCEEDED` state.


Watching these three API calls succeed (`POST /payment_instruments`, `POST /transfers` or `POST /authorizations`, and the subsequent capture if applicable) is the authoritative proof that the integration works end-to-end. The Finix Dashboard will reflect the Transfer / Authorization once your backend creates them.

### 3D Secure (optional)

If you enabled 3DS in [Step 9](/android/online/integration#9-enable-3d-secure-optional):

1. Submit a 3DS-required test card. The SDK should present the issuer's WebView challenge inside the sheet.
2. Complete the challenge (the sandbox issuer typically auto-passes). Confirm `onSuccess` fires with a non-null `response.threeDSResponse?.sessionId`. A session ID starting with `3d_secure_session_` means authentication succeeded.
3. Submit a 3DS-failing test card. Confirm `onFailure` fires with [`FinixErrorCode.ThreeDSFailed`](/android/online/errors#finixerrorcode) carrying a non-null `failureCode`.


## Checklist

- [ ] Tokenization succeeds with a sandbox card and `onSuccess` returns a `TK...` ID.
- [ ] Tokenization fails cleanly with a decline card - `onFailure` fires with a [`FinixErrorCode`](/android/online/errors) variant you handle.
- [ ] Your backend creates a Payment Instrument from the token and a Transfer (or Authorization) from the Payment Instrument.
- [ ] The resulting Transfer / Authorization is visible in the Finix Dashboard.
- [ ] If using 3DS: a `3d_secure_session_...` session ID is forwarded to your backend alongside the token and recorded on the Transfer / Authorization.


Once all five boxes are green against Sandbox, swap to `PaymentSheetEnvironment.LIVE` + Production Application ID and repeat the token-only checks with a small real-card transaction before going live.