Skip to content

Instantly share code, notes, and snippets.

@shrodingers

shrodingers/needs for payments refactor.md

Created May 10, 2019 07:51
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save shrodingers/f983343d1c8b391d13f720b62d4612f6 to your computer and use it in GitHub Desktop.
Save shrodingers/f983343d1c8b391d13f720b62d4612f6 to your computer and use it in GitHub Desktop.
Download ZIP
needs for payments refactor
Raw
needs for payments refactor.md

Stripe connect product needs

  • How to make users give their payment data ?
  • How to make users give their ID data ? (same place as payments ?).
  • How to warn users when data are invalidated (for them to update them asap) ?
  • Can we use the brigad's customer account strategy on stripe in order to pay brigaders when balance is not sufficientb?
  • Which statuses shall we have with the new payment service ?
  • Need to know if possible to reduce the delays with stripe for connected accounts
  • Need to separate invoicing data from payment data (new tabs ?)

BACS product needs

  • How to design new tab for bacs in uk ?
  • Need to implement adviced workflow in GoCardless docs
  • Need to be validated by GoCardless team
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment