1
0
Fork 0
mirror of https://we.phorge.it/source/phorge.git synced 2024-12-19 12:00:55 +01:00

Use more reassuring UI and copy for removing payment methods

Summary:
The old treatment was fairly technical. Give this UI a more human-friendly flow:

  - Use language "remove" instead of "disable". We keep the record that the card existed around for auditing/historical purposes, but it is no longer a valid payment method going forward and can not be undone. I think this aligns with user expectation and actual behavior better than "disable".
  - Only show active methods on the profile screen.

Test Plan: {F1057153}

Reviewers: chad

Reviewed By: chad

Differential Revision: https://secure.phabricator.com/D14973
This commit is contained in:
epriestley 2016-01-08 09:18:53 -08:00
parent 0dd947cced
commit 2fcf571bfd
2 changed files with 8 additions and 5 deletions

View file

@ -132,6 +132,10 @@ final class PhortuneAccountViewController extends PhortuneController {
$methods = id(new PhortunePaymentMethodQuery())
->setViewer($viewer)
->withAccountPHIDs(array($account->getPHID()))
->withStatuses(
array(
PhortunePaymentMethod::STATUS_ACTIVE,
))
->execute();
foreach ($methods as $method) {

View file

@ -38,11 +38,10 @@ final class PhortunePaymentMethodDisableController
}
return $this->newDialog()
->setTitle(pht('Disable Payment Method?'))
->setShortTitle(pht('Disable Payment Method'))
->setTitle(pht('Remove Payment Method'))
->appendParagraph(
pht(
'Disable the payment method "%s"?',
'Remove the payment method "%s" from your account?',
phutil_tag(
'strong',
array(),
@ -50,9 +49,9 @@ final class PhortunePaymentMethodDisableController
->appendParagraph(
pht(
'You will no longer be able to make payments using this payment '.
'method. Disabled payment methods can not be reactivated.'))
'method.'))
->addCancelButton($account_uri)
->addSubmitButton(pht('Disable Payment Method'));
->addSubmitButton(pht('Remove Payment Method'));
}
}