Manual Refund Process Flow

[David Bialer]

I am writing some specs for developer facing and Mozilla facing requirements regarding refunds and chargebacks and was hoping you might be able to shed some light on a few issues:

1. When a user requests a refund from a developer (by contacting them as in User Story PayAndID-011), how is the user able to identify the transaction to the developer? (Do they need to be exposed to a transaction ID in the Purchase History?). This is outside the automated 30min refund. We still need a refund path for developers (or Mozilla) to be able to issue a refund. Web Payment Receipts spec has a 'detail' field - are we using to store a transaction ID, and if so, how would a user be able to know this?

2. If a refund is manually issued asynchronously (manually), is the Marketplace ever able to invalidate the receipt on the device or is this the responsibility of the app to validate a receipt through the receipt validation API? (i.e. the receipt never gets removed and shows up in purchase history). Also app removal, I assume, doesn't happen?

Thanks,
David

[Andy McKay]

On Nov 6, 2012, at 10:07 AM, David Bialer <dbi...@mozilla.com> wrote:

> 2. If a refund is manually issued asynchronously (manually), is the Marketplace ever able to invalidate the receipt on the device or is this the responsibility of the app to validate a receipt through the receipt validation API? (i.e. the receipt never gets removed and shows up in purchase history). Also app removal, I assume, doesn't happen?

The marketplace cannot invalidate a receipt on the device. It's up to the app to check the receipt and when it does so it will find that it has been removed.

If there is an app is uninstalled then the receipt is removed at that time.

[Kumar McMillan]

On Nov 6, 2012, at 12:07 PM, David Bialer wrote:

> I am writing some specs for developer facing and Mozilla facing requirements regarding refunds and chargebacks and was hoping you might be able to shed some light on a few issues:
>
> 1. When a user requests a refund from a developer (by contacting them as in User Story PayAndID-011), how is the user able to identify the transaction to the developer? (Do they need to be exposed to a transaction ID in the Purchase History?). This is outside the automated 30min refund. We still need a refund path for developers (or Mozilla) to be able to issue a refund. Web Payment Receipts spec has a 'detail' field - are we using to store a transaction ID, and if so, how would a user be able to know this?

Whoops, I just saw this in another thread on this. I think we can make this easier: the user could click a link from the Marketplace purchase history to initiate a manual refund. This could email the developer so they can review the request and click a link to complete the refund if they want to.

>
> 2. If a refund is manually issued asynchronously (manually), is the Marketplace ever able to invalidate the receipt on the device or is this the responsibility of the app to validate a receipt through the receipt validation API? (i.e. the receipt never gets removed and shows up in purchase history). Also app removal, I assume, doesn't happen?
>

> Thanks,
> David
> _______________________________________________
> dev-marketplace mailing list
> dev-mar...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-marketplace

[Maria Sandberg]

> Whoops, I just saw this in another thread on this. I think we can make this easier: the user could click a link from the Marketplace purchase history to initiate a manual refund. This could email the developer so they can review the request and click a link to complete the refund if they want to.

We are moving away from keeping a full purchase history in the Marketplace to sending email receipts. Could we have the same behavior but from the email?

---
Maria Sandberg
UX Designer, Fx Marketplace
Mozilla Corporation