[gpl1]

We'd also like to add CNAME support so you could have pro.yoursite.com show the payment page you make on PintPay. We're also working on an api and webhook / URL postback for info about changes/notifications/cancellations on subscriptions. A lot still to do during the beta!

[aeden]

The problem with using CNAME records in this way is that the resulting page would not be protected under SSL. Even if the resulting POST is, there are reasons to ensure that page 1 is also under SSL, such as verification that the page comes from who it says, that it wasn't altered during transmission, and simply as a matter of perception. With a CNAME record unless the domain holder provided you with an SSL certificate and you are able to do multi-homed SSL, then you're going to have to run in under normal HTTP, and with a payment system you really do need all of the pages under SSL.