Last Updated: 06 October 2025 | Change Log
AccessCheckoutEditText
is an Android UI component that wraps an EditText
for the purpose of entering card details.
To ensure you remain SAQ-A compliant, we have designed the AccessCheckoutEditText
component to not publish any methods or properties that expose the text entered by the end user.
You can customize your views using the following properties and methods supported by AccessCheckoutEditText
.
In addition to the XML properties supported by the View
class, here are the properties supported by AccessCheckoutEditText
:
Properties | Type |
---|---|
android:textColor | Color |
android:hint | String |
android:textColorHint | Color |
android:imeOptions | Int |
android:cursorVisible | Boolean |
android:textSize | Float |
android:font | Typeface |
android:autofillHints | String |
In addition to the methods supported by the View
class, here are the methods supported by AccessCheckoutEditText
, along with the minimum API level required for each method:
Methods | API level |
---|---|
getHint():CharSequence | 21 |
setHint(value:CharSequence) | 21 |
isEnabled():Boolean | 21 |
setEnabled(value:Boolean) | 21 |
getCurrentTextColor():Int | 21 |
setTextColor(value:Int) | 21 |
getCurrentHintTextColor():Int | 21 |
setHintColor(value:Int) | 21 |
getImeOptions():Int | 21 |
setImeOptions(value:Int) | 21 |
getTextSize():Float | 21 |
setTextSize(value:Float) | 21 |
getTypeface():Typeface | 21 |
setTypeFace(value:Typeface) | 21 |
isCursorVisible():Boolean | 21 |
setCursorVisible(value:Boolean) | 21 |
setText(text:String) | 21 |
setAutofillHints(hints: String) | 26 |
getAutofillHints():Array<String> | 26 |
setOnFocusChangeListener(event: OnFocusChangeListener) | 21 |
getOnFocusChangeListener(): OnFocusChangeListener | 21 |
setTextAppearance(@StyleRes resId: Int) | 23 |
setAutoSizeTextTypeWithDefaults(@TextViewCompat.AutoSizeTextType autoSizeTextType: Int) | 26 |
clear() | 21 |
There are methods from the View
class which are not supported, these are:
Methods not supported |
---|
getBackgroundTintList():ColorStateList |
setBackgroundTintMode(PorterDuff.Mode tintMode) |
setBackgroundTintBlendMode(BlendMode blendMode) |
AccessCheckoutEditText
is compatible with android:autofillHints
. Providing autofillHints
enables the autofill service to recognize the type of view, making it possible for your customer to enter credit card details automatically in your application.
You can set autofill hints using the android:autofillHints
attribute. The following example sets a "creditCardNumber" hint on an AccessCheckoutEditText
:
<com.worldpay.access.checkout.ui.AccessCheckoutEditText
android:layout_width="match_parent"
android:layout_height="wrap_content"
app:layout_constraintTop_toTopOf="parent"
android:autofillHints="creditCardNumber"/>
You should assign the appropriate autofill hint to each AccessCheckoutEditText
input field based on its purpose. Use:
creditCardNumber
for the card number fieldcreditCardExpirationDate
for the expiry datecreditCardSecurityCode
for the credit card security code (CVC/CVV)
You can also set hints programmatically using the setAutofillHints() method, as shown in the following example:
val creditCardNumber = findViewById<EditAccessCheckoutEditTextText>(R.id.credit_card_number)
creditCardNumber.setAutofillHints(View.AUTOFILL_HINT_CREDIT_CARD_NUMBER)
AccessCheckoutEditText
has support for onFocus
events, allowing your application to update the UI dynamically when your customer interacts with the AccessCheckoutEditText
.
You must use the setOnFocusChangeListener
method to react to focus changes.
The example below changes the background of the AccessCheckoutEditText
when the field gains focus to the secondary color and changes it back to the primary color when the field loses focus.
val panText = view.findViewById(R.id.credit_card_number)
panText.setOnFocusChangeListener { view, hasFocus ->
val color = if (hasFocus) R.color.design_default_color_secondary else R.color.design_default_color_on_primary
view.setBackgroundColor(ContextCompat.getColor(requireContext(), color))
}
AccessCheckoutEditText
acts as a wrapper around an EditText
. This is to ensure you can't access the EditText
instance and remain SAQ-A compliant.
Because of this, you must perform an action on the EditText
rather than on the AccessCheckoutEditText
instance.
You can access the EditText
instance in Espresso by using the code below, where the id corresponds to the id of the AccessCheckoutEditText
instance:
Espresso.onView(ViewMatchers.withParent(withId(R.id.your_identifier)))