Deploying payments (membership and h branding) features

This is the proposed process for deployment to production (all steps occur on production server):

1. Deploy latest release using usual procedure

2. Run migrations

3. Bootstrap member status and 2017 payments:

rake shf:users:set_member_status
rake shf:payments:membership_2017
rake shf:payments:branding_2017

Results should be see in stdout. Also, confirm by checking logs:

users_member_status
membership_payment_2017
companies_branding_payment_2017

Confirm data changes by checking:

- User member status in users `index` view.
- Member payment status in user `show` view.
- Company payment status in company `show` view.

4. Test membership payments using dev/test HIPS account (use test SHF (member) account or admin account)

   • In .env, set these ENV vars to the values for the dev HIPS account:

     • HIPS_PRIVATE_KEY
     • HIPS_PUBLIC_KEY

   • Start the app, login, go to user show view, execute membership payment using HIPS test credit card

   • Confirm expire date has been advanced to Dec 31, 2018.

   • Confirm webhook activity in HIPS.log.

   • In rails console, delete the Payment record created by this test.

5. Test branding payments using dev/test HIPS account

   • Procedure essentially same as step 4, except using company show view.

6. Test membership payments using real HIPS account (using Test sales channel)

   • Procedure same as step 4, except using public and private keys for "real" SHF HIPS account, Test sales channel.

7. Test branding payments using real HIPS account (using Test sales channel)

   • Procedure same as step 5, except using public and private keys for "real" SHF HIPS account, Test sales channel.

8. Set ENV values for real HIPS account, Live sales channel.

   • Confirm payment form for membership payments appears
   • Confirm payment form for H-Branding payments appears

9. Optional: test payment(s) using real HIPS account (_Live) channel) and process actual payment

   • Credit card, invoice, SWISH