Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 Force a manual payment from the backend? | Event Espresso - Staging Server
Is there a way for us to enter a client’s credit card number into the system on her behalf and therefore have her account status change to “payment received”? I know how to adjust the payment status, but don’t know how to manually input her cc#. She got so confused with the checkout process (PayPal PRO was accidentally turned on as well as regular PayPal, but the CC options weren’t showing in the dropdown), that she just gave her CC# to my client and my client said she’d “take care of it.” However, short of creating a dummy registration where we can input the CC# and then delete the dummy registration, we don’t know how to do it. I know there is a generated link with the shortcode [invoice_link], but I don’t know how to get that invoice link without emailing the customer. Suggestions? Thanks!
With the current payment gateways I don’t believe thats possible. Your client would need to have a merchant account of some sort where he process credit cards directly, without the need of the user to provide passwords etc.
The buyer will need to process it via the payment gateway (paypal), or you will need to invoice them to get a cheque or use a direct bank transfer.
Viewing 1 reply thread
The support post ‘Force a manual payment from the backend?’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.