Home → Questions →

Dynamically generate credit card update URL in payment declined emails

• Edit

Adam

17 Jun, 2010 03:41 PM

Hi. When we have cards declined or expiration notices that go out, we'd love to include a URL such that clients could update their information. Is that supported natively in the app?

Thanks,
Adam

1. Support Staff 1 Posted by Marc Guyer on 17 Jun, 2010 03:52 PM

   

   There is a "Customer Account URI" setting here: https://cheddargetter.com/admin/configuration/settings

   Then, in email templates, this value can be embedded using {$customerAccountUri}. You could attach anything to it that you choose (e.g., {$customerAccountUri}?myId={$customerCode}).

   For other vars not included in CG natively, you may choose to use the meta data feature: http://support.cheddargetter.com/faqs/api-8/customer-meta-data. Note the Using Meta Data in Email Templates section.

   • Edit

2. 2 Posted by Adam on 17 Jun, 2010 03:59 PM

   

   Hi Marc,

   Quick question: What would a URL look like that would actually send someone
   to a CheddarGetter hosted page to do their update?

   Thanks!
   Adam

   • Edit

3. Support Staff 3 Posted by Marc Guyer on 17 Jun, 2010 04:07 PM

   

   We don't currently support a CG-hosted page for this purpose. We are working on it right now, however. It should be available in 3-6 weeks. When that's complete, CG will generate the link for you in the email.

   • Edit

4. Marc Guyer closed this discussion on 17 Jun, 2010 04:07 PM.

5. Adam re-opened this discussion on 17 Jun, 2010 05:01 PM

6. 4 Posted by Adam on 17 Jun, 2010 05:01 PM

   

   Excellent. That would be just what we need.

   Are there any plans to allow:

   1. Domain mapping (e.g. a CName pointing to your servers)
      
   2. SSL support in the case of domain mapping

   Thanks!
   Adam

   • Edit

7. Support Staff 5 Posted by Marc Guyer on 17 Jun, 2010 07:26 PM

   

   CNAME would require SSL. In that case, purchase of a certificate and manual server config would be required. That would incur a hefty upfront fee and a recurring charge. In other words, it is possible but there isn't a plan for it right now. If it was just CNAME, it would be seamless but SSL is required.

   • Edit

8. Marc Guyer closed this discussion on 17 Jun, 2010 07:26 PM.

9. Adam re-opened this discussion on 17 Jun, 2010 07:47 PM

10. 6 Posted by Adam on 17 Jun, 2010 07:47 PM

    

    Sounds good. Thanks!

    • Edit

11. Dean closed this discussion on 16 Jan, 2013 02:57 PM.