Demo: October 9
Agenda
- Credit card validation on payment plan creation
- Multiple payments bug
- Ongoing related records work
- Discuss Nashville marketing
Credit card validation on payment plan creation
Eric reports that case “Adam Bihon” — credit card number was given to him wrong. He was able to setup a plan, but it later failed to charge, b/c card number was wrong.
We validate credit card numbers on payment plan creation.
Stripe validates card information when it is saved. As a result of this process, customers may see a temporary authorization for $1 on their statement. This does not guarantee that any future charges succeed (e.g., the card no longer has sufficient funds, is reported lost or stolen, or if the account is closed). This process also updates the results of any checks, including traditional bank checks by Radar (e.g., CVC or ZIP code), that may have been performed.
Note Adam Bihun is the customer where the original payment plan was missing an email.
Outcomes
- added: required email address on payment plan creation.
Multiple payments bug
https://portal.siegelcallahan.com
- Note: we use a Stripe provided component to receive and process credit card number.
- We blocked the submit button with JavaScript, yet some multiple POSTs were able to get through.
- Ordinarily, Rails (our framework) would disable the form after submission; but the Stripe component undermines this.
- Disabling (and reenabling on error) has to be handled manually.
- Couple that with a second or two of delay making the stripe request for token and customer impatience, explains multiple charges.
Outcomes
- Improved disabling and reenabling (on staging: https://sc-portal-staging.herokuapp.com)
- Stripe is nudging all customers towards their integrated (hosted) Stripe Checkout product (hosted).
- Demo: https://stripe.com/docs/payments/checkout
- Recommendation: test and launched improved disabling / renabling form before migrating to checkouts.
Client / Property related records
