Yep, that's what I had in mind, especially because the BraintreeError case is almost always due to bad user input on the credit card form. So people might end up doing something like:

    switch err {
        case BraintreeError: // redirect user back to CC form with err.Error() as the message
        default: // display a 500
    }