Android SDK
- Installation
- Primer
- PrimerHeadlessUniversalCheckout
- Methods
- Listeners
- Assets Managers
- Native UI manager
- Raw Data manager
- Raw Data Manager Listener
- NOL Pay manager
- Component With Redirect manager
- Klarna Headless manager
- ACH Headless manager
- Vault manager
- Logging
- Common objects
On this page
provideNolPayLinkCardComponent
This method allows you get a new instance of
NolPayLinkCardComponent that can be used to link new
nol Pay cards.
KOTLIN
Copy
Ask AI
fun provideNolPayLinkCardComponent(viewModelStoreOwner: ViewModelStoreOwner): NolPayLinkCardComponent
Parameters
Hide Parameters
Hide Parameters
The ViewModelStoreOwner
to associate with the component.
Returns
An instance ofNolPayLinkCardComponent.
Hide NolPayLinkCardComponent
Hide NolPayLinkCardComponent
start()
Initialize the component by calling the start function. This method should be called only once.
updateCollectedData(collectableData: NolPayLinkCollectableData)
Update component with collected data by passing implementations of sealed interface representing collectable data for linking a nol Pay card.
This method can be called at any point, even if you have only partially collected data.
To validate the partially collected data, you can refer to the
componentValidationStatus
and receive the validation status when it’s updated.
Show sealed interface NolPayLinkCollectableData
Show sealed interface NolPayLinkCollectableData
NolPayTagData
Data class representing nol Pay tag data collected during the linking process.
Hide Properties
Hide Properties
An NFC tag decoded using NolPayNfcComponent.
NolPayPhoneData
submit()
Call
submit function in order to process collected data and move component to next state.componentStep: Flow<NolPayLinkCardStep>
NolPayLinkCardStep is a class holding different output data for specific steps. Whenever
start or submit methods are
called,
componentStep will trigger the next step in case the call to the mentioned method was successful.
Show sealed interface NolPayLinkCardStep
Show sealed interface NolPayLinkCardStep
CollectTagData
Object representing the step of collecting tag data for nol Pay card linking.
CollectPhoneData
A data class representing the step of collecting phone data for nol Pay card linking.
Hide Properties
Hide Properties
The card number associated with the nol Pay card scanned in
CollectTagData step.CollectOtpData
A data class representing the step of collecting OTP (One-Time Password) data for nol Pay card linking.
Hide Properties
Hide Properties
The mobile number to which OTP code was sent to.
componentValidationStatus: Flow<PrimerValidationStatus<NolPayLinkCollectableData>>
The
PrimerValidationStatus interface encompasses a range of validation statuses.Show sealed interface PrimerValidationStatus
Show sealed interface PrimerValidationStatus
Validating<NolPayLinkCollectableData>
Indicates that data is currently in the process of being validated.
Hide Properties
Hide Properties
The data being validated.
Valid<NolPayLinkCollectableData>
Indicates that the data has successfully been validated.
Hide Properties
Hide Properties
The successfully validated data.
Invalid<NolPayLinkCollectableData>
Indicates that the data has been considered invalid after validation.
Hide Properties
Hide Properties
List of
PrimerValidationError objects that represent data validation errors emitted by this component.The data that failed validation.
Error<NolPayLinkCollectableData>
Represents the status when an error occurred during the validation process.
Hide Properties
Hide Properties
The specific
PrimerError that occurred during validation.Show PrimerValidationError
Show PrimerValidationError
A unique error identifier.
A unique error code.
A error description.
A recovery suggestion for the given error. In case it’s present, use it to try
to recover from error.
A unique diagnostics id for the given error.
The data for which the error occurred.
componentError: Flow<PrimerError>
Get a Flow
of PrimerError objects that represent errors emitted by this component.
Subscribers can observe and handle errors using this Flow.
Assistant
Responses are generated using AI and may contain mistakes.