In many scenarios within the sharing economy such as car sharing or bike sharing a customer's mobile device is an essential part in the service delivery and payment system. Card credentials are often getting stored with the cardholder’s account at the service provider for optimal user experience.

The sequence of actions to be performed are outlined in the diagrams below.

Card Add as part of a none payment transaction (NPA)

Card Add as part of a payment transaction

Service Provisioning

Amount

Card Add

A zero amount or any estimated amount. Please note that the amount is usually displayed to the cardholder during an authentication challenge and thus, should be within the customer’s reasonable expectation.

Service Provisioning

The amount in the authorization request should be an estimated for the service provision according to resonable customer expectations. Once the service has been completed incremental authorizations may be used before the final amount is captured.

credentialOnFile

Card Add

The UCOF flag is submitted to establish a mandate for storing the credentials and to obtain an initial schemeReferenceID. The card issuer is obliged to perform a step-up during authentication.

{
    "type": {
        "unscheduled": "CIT"
    },
    "initialPayment": true
}

Service Provisioning

The CIT flag is submitted in order to enable UCOF transactions without card security value.

{
    "type": {
        "unscheduled": "CIT"
    },
    "initialPayment": false
}

AccVerify

All Card Adds that are not performed as part of a payment transaction require and account verification.