# Save Card on File using Push Account Receipt
source: https://developer.mastercard.com/mastercard-checkout-solutions/documentation/use-cases/push-prov/scof-push-acc-receipt/index.md

For secure and convenient online checkouts consumers can push their cards from their issuers website or mobile banking app to Integrators participating in Secure Card on File.  

The following use case explains how Integrators can enroll consumer cards into Secure Card on File using `pushAccountReceipt`, this requires that the Issuer interacts with MDES.
Diagram complete_pushaccountreceipt

1. The consumer is logged in to their issuer's app or website.
2. They select the Secure Card on File Integrator (merchant in this use case) and the card to push.
3. Using [MDES Token Connect API](https://developer.mastercard.com/mdes-digital-enablement/documentation/use-cases/push-provisioning-merchant-use-case/), the issuer contacts MDES to request the push of the selected card to the target Token Requestor.
4. MDES generates and returns a `pushAccountReceipt` to the issuer.
5. The issuer interface selects the URI provided by the Integrator and appends the URI with the `pushAccountReceipt` of the card being pushed and the `callback URL`: the issuer URL that the Token Requestor must call out upon completion of tokenization to return the consumer to the issuer's interface.
6. The issuer interface invokes the Integrator's app or website with the appended URI.
7. The Integrator interface may request the consumer to sign in or sign up.
8. Upon successful log in, Integrator enrolls the card with the `pushAccountReceipt` into Secure Card on File. The Integrator calls the [Enroll](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/api-reference/apis/index.md#card)) API with `enrolmentReferenceType` set to `PUSH_ACCOUNT_RECEIPT`.
9. If enrollment is successful, the `DigitalCardData.status` is set to `ACTIVE` in the enroll card response returned to the Integrator.
10. The Integrator includes the `pushAccountReceipt`, with their respective results, in the callback URL that the issuer interface provided. The Integrator invokes the resulting URI, and the consumer is taken back to the issuer app or website.