---
page_title: Description
product: CRED Saved Cards
page_source: https://juspay.io/in/docs/cred-saved-cards/docs/cred-saved-cards/description
llms_txt: https://juspay.io/in/docs/llms.txt
product_llms_txt: https://juspay.io/in/docs/cred-saved-cards/llms.txt
---


# Description



CRED Saved Cards removes that friction by making the card vault CRED has already built available directly on your checkout.


## Feature specification




| Parameter | Details |
|---|---|
| Gateway | Supports each gateway |
| Juspay's role | Token Service Provider (TSP) |
| Supported networks | Visa, Mastercard, RuPay |
| Authentication | D-OTP, collected natively within the CRED app |
| Minimum Android SDK version | 3.95 and above |



## Device tokenization



When a customer saves a card on CRED, CRED creates two linked tokens:

* A **network token** : issued by the card network (Visa or Mastercard)
* A **CRED’s device token** : bound to the customer's specific device hardware and protected by biometric authentication

CRED cards are linked to a specific device:

* **Android** : a customer who switches phones starts fresh on the new device
* **iOS** : this applies even on the customer's primary device cards are only shown after the customer has completed at least one payment through the Link & Pay flow on that device


## CRED Saved Cards Flow 



Sequence diagram showing CRED Saved Cards flow across Merchant Server, Merchant SDK, Juspay SDK, and Juspay Server. 

* Phase 1: `containerAvailability` and containerEligibility.
* Phase 2: order creation.
* Phase 3: `containerTxn` invoking the CRED app.
* Phase 4: `orderStatus` confirmation.

![Image](https://dth95m2xtyv8v.cloudfront.net/tesseract/assets/cred-unbundling/Cred%20Unbundling%20%20(3)-L04TX.png)
*CRED Saved Cards flow*

### Mermaid code for the above image

```mermaid
sequenceDiagram
    autonumber

    participant MS as Merchant Server
    participant SDK as Merchant SDK
    participant JSDK as Juspay SDK
    participant JS as Juspay Server

    MS->>SDK: Fetch customer ID, phone number, etc.

    SDK->>JSDK: containerAvailability
    Note right of JSDK: Checks CRED app presence<br/>and fetches device ID
    JSDK-->>SDK: containerAvailability Response

    SDK->>JSDK: containerEligibility
    Note right of JSDK: Eligibility + Cards Discovery
    JSDK-->>SDK: containerEligibility Response

    Note over SDK: Show link option / list cards<br/>based on eligibility response

    Note over SDK: User selects payment option

    SDK->>MS: Order Initiation

    MS->>JS: orderCreate
    JS-->>MS: orderCreate Response

    MS->>SDK: Order Details

    SDK->>JSDK: containerTxn

    Note right of JSDK: Invokes CRED app and<br/>completes transaction

    Note right of JSDK: Links user if not already linked

    JSDK-->>SDK: containerTxn Response

    MS->>JS: orderStatus
    JS-->>MS: orderStatus Response
```




### **Integration Flow Overview** 



* Merchant Server fetches customer details and passes them to the Merchant SDK.
* Merchant SDK calls Juspay SDK to check CRED app availability and customer eligibility.
* On user payment intent, Merchant Server creates an order via Juspay Server API.
* Merchant SDK triggers containerTxn in Juspay SDK, which invokes the CRED app to complete the transaction.
* Merchant Server polls Juspay Server for final order status confirmation.

---

## See Also

- [Overview](https://juspay.io/in/docs/cred-saved-cards/docs/cred-saved-cards/overview)
- [Get Started](https://juspay.io/in/docs/cred-saved-cards/docs/cred-saved-cards/get-started)