> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/psdk-latest/psdk-user-guide-and-training/psdk-training-videos/android-architecture.md).

# Android Architecture

{% embed url="<https://vimeo.com/1127710558/3ffc57a9d5>" %}

**Transcript**:

To better understand the integration of Verifone's payment terminals with your app, learning the basics is crucial. I will provide a general overview to get you started. It will include: the devices that support PSDK integration, how the Processor works, and which are the differences between Verifone's devices. In following videos, we will dive into the specifics tailored to your choice of integration.

Let's start by introducing Verifone's Android devices that are being supported today.

We have the T650 devices that include what you could find as T650c or T650p; the P630, the V660, UX700, M425, the M450. And our new Victa devices: the Victa Portable, Victa Mobile and Victa Reader, which you can see here displayed with a mobile phone since it can be used with Android and Apple devices.

<figure><img src="/files/UJxMP6meQvygjhYKYKCl" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/rihNrDnoIKTIrfA7SQX7" alt=""><figcaption></figcaption></figure>

All of these devices support Verifone's Payment SDK integration, and because of their internal architecture, you can seamlessly migrate the software between the terminals.

Now let's talk about the architecture

<figure><img src="/files/Y5JfSx7kKzT3E7r5C8BV" alt=""><figcaption></figcaption></figure>

Android devices use a dual-processor architecture to protect sensitive information during application processing. The Android Application Processor and the Secure Processor work independently, ensuring that cardholder data remains encrypted and is never exposed in plain text. Sensitive information, such as PINs, is also managed exclusively by the Secure Processor, entirely bypassing the Android environment.

Verifone's payment terminals work with 4 components: A Processor; a Dual OS; a Key Store where the sensitive information is stored securely; and Key Loading since we need to inject the keys to encrypt the data.

Our devices work very similar between each other, the differences we find are in the Processor they use, specifically for the T650 devices use a Qualcom SD 210 Cortex A7 Processor, while the rest use a QCM 2150 Cortex A53 Quadcore Processor

They will all be using use a K81 secure processor, a Keystore on Android that encrypts the keys, and for Key Loading they will all use VRK, Verifone Remote Key Loading .

<figure><img src="/files/SxdZmcNWKcGCLM0v4SiC" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verifone.com/psdk-latest/psdk-user-guide-and-training/psdk-training-videos/android-architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
