Page MenuHomePhabricator

Adjust payment workflows to deal with merchants and configurable providers in Phortune
ClosedPublic

Authored by epriestley on Oct 7 2014, 8:08 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 11, 8:33 AM
Unknown Object (File)
Tue, Apr 9, 11:45 AM
Unknown Object (File)
Thu, Apr 4, 7:46 AM
Unknown Object (File)
Thu, Apr 4, 7:46 AM
Unknown Object (File)
Thu, Apr 4, 7:44 AM
Unknown Object (File)
Thu, Apr 4, 7:27 AM
Unknown Object (File)
Mon, Apr 1, 4:13 PM
Unknown Object (File)
Thu, Mar 28, 7:05 PM
Subscribers

Details

Summary

Ref T2787. Builds on D10649 by rebining existing objects (carts, charges, etc) to merchantPHIDs and providerPHIDs instead of an implicit global merchant and weird global artifacts (providerType / providerKey).

Basically:

  • When you create something that users can pay for, you specify a merchant to control where the payment goes.
  • Accounts are install-wide, but payment methods are bound to merchants. This seems to do a reasonable job of balancing usability and technical concerns.
  • Replace a bunch of weird links between objects with standard PHIDs.
  • Improve "add payment method" flow.
Test Plan

Went through the Fund flow with Stripe and WePay, funding an initiative.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Adjust payment workflows to deal with merchants and configurable providers in Phortune.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Oct 7 2014, 9:40 PM
This revision was automatically updated to reflect the committed changes.