**Last updated**: 30 October 2025 | [**Change log**](/products/checkout/ios/changelog/)

# AccessCheckoutUITextField

You can customize your views. Here are the properties supported by our components:

## Properties

In addition to the `UIView` class, here are the properties supported by our component:

| Properties | Type |
|  --- | --- |
| accessibilityHint | String |
| accessibilityIdentifier | String |
| accessibilityLabel | String |
| accessibilityLanguage | String |
| cornerRadius | CGFloat |
| borderColor | UIColor |
| borderWidth | CGFloat |
| textColor | UIColor? |
| font | UIFont? |
| textAlignment | NSTextAlignment? |
| placeholder | String? |
| attributedPlaceholder | NSAttributedString? |
| keyboardAppearance | UIKeyboardAppearance |
| isEnabled | Boolean |


## Methods

 To ensure you remain SAQ-A compliant, the `AccessCheckoutUITextField` component has been designed to not expose any methods or properties to retrieve the text entered by the end user. 

In addition to the `UIView` class, here are the methods supported by our component:

| Methods |
|  --- |
| clear() |
| becomeFirstResponder():Boolean |
| resignFirstResponder():Boolean |


# Use XCUI for UI testing

`AccessCheckoutUITextField` acts as a wrapper around a `UITextField`. This is to ensure you can't access the `UITextField` and remain SAQ-A compliant.

Because of this, you must perform an action on the `UITextField` rather than on the `AccessCheckoutUITextField`.

You can access the `UITextField` by using the code below, where `your-identifier` corresponds to the id of the `AccessCheckoutUITextField`:


```
XCUIApplication().otherElements["your-identifier"].textFields.firstMatch
```