Shopify used to allow you to style the checkout process through a CSS file. However, they have now removed this option.
I've developed a Shopify App for a customer that requires that ALL customers digitally sign a form before payment. The form asks specific questions, and must be presented in a specific way, with a specific font. In their country it is illegal to sell online without sending your customers through this process. Everything is sent over TLS etc.
On the form, a customer is asked their name, delivery address, billing address, etc. The products are listed and followed by a ton of legal text.
The difficulty is, as soon as the customer goes to checkout - they are then able to change their delivery and billing address, thus rendering the form null and void.
My initial thought was to simply hide the customer billing and delivery information from the checkout using CSS. However, I'm unable to do this because Shopify no longer grant access to the style sheet.
Does anyone know of a way around this?
Related
I have product designer software in my website that currently allows customers to design a product and get a live price. The software has the ability to send a message to the parent of an iframe where the information can be processed as I like. I want this information to be sent to my sagepay, worldpay or stripe payment gateway to give the customers the ability of purchasing the product.
Does anyone have any idea how to achieve this or even where to start!
Thanks in advance
Dan
Most payment gateways allow somehow to send the details of the purchased products details via API when processing the payment.
For SagePay (if you mean the one which currently is labeled as Opayo by Elavon) you may use the detailed basket via XML or CSV. Or you may simply use the common Description field.
For Worldpay it's the instruction.narrative.line1 field from the authorization request.
And for Stripe it should be either metadata or payment_intent_data objects.
I need to do a reservation for 3 restaurants- in each there are 12 tables. Some of the reservations have to be paid before, the rest of them not at all.
Also, there is a need to identify if in the particular restaurant there is a reservation for different events- then the functionality of not-paid reservation must be switch off.
Ideally, if mails with reservations should be delivered to various email addresses - based on the name of the restaurant.
Everything must run on WP.
Can you please assist me with that?
For this system, I suggest you this solution.
I should say that using this answer requires average knowledge of PHP and WordPress functions.
Create a custom post type for Restaurants.
Information such as not-paid reservation, paid reservation, and events can be saved as meta values.
To save meta values for your custom post type, you can use the "advanced custom fields" plugin or just code them using add_meta_box().
For the reservations, you should make a form and in the form, users can select their reservation table, date, and time.
if the reservation requires payment, you should check the gateway documentation and use their script.
here you need to create a table in the database for payments.
after the form submits and before payment, add your user info to the database and give the payment status "pending" value.
after the successful or unsuccessful payment, the gateway will return the payment status and with that, you can save the reservation status.
For sending an email to the restaurant manager, after the successful payment, use wp_mail().
I tried to explain the whole project to you in 12 lines so, after reading this answer you may get confused.
If you have more questions, just ask.
We have generated one RSS feed and submitted to itunes few months ago. Now we realised we have added the wrong email. So can we update the email id in our rss feed? If we update in our rss feed, Do we need to submit again? please let us know about this. Thank you.
<itunes:owner>
<itunes:name>FeedForAll</itunes:name>
<itunes:email>abc#abc.com</itunes:email>
</itunes:owner>
Here is a snippet from Apples's doco on podcast rss feeds...
<itunes:owner>
The podcast owner contact information.
Include the email address of the owner in a nested <itunes:email> tag
and the name of the owner in a nested <itunes:name> tag.
Note: The <itunes:owner> tag information is for administrative
communication about the podcast and isn’t displayed in Apple Podcasts.
Please make sure the email address is active and monitored.
Once Apple has verified the ownership and quality of your rss feed (i.e. through the podcast submission process) then your podcast is active in their directory.
From that point you are free to update your feed however you like, as long as your updates continue to conform to Apple's rss feed requirements.
In this case, if you update the value of the <itunes:email> then the change should automatically be picked up during the next feed refresh. i.e. you shouldn't need to resubmit.
Note: you should still use a valid email address in that tag so that people can contact you if there are issues with your feed, or they genuinely want to get in touch, etc. If you are worried about spam, then perhaps use an email address that different from your day-to-day address. i.e. One that you can access/check when you need to but that won't bother you if it gets hit with spam. You can drop in there and check it/clear it out occasionally as needed.
Also worth thinking about. Other podcast directories sometimes rely on email addresses in rss feeds in order to verify ownership. E.g. this is how Google uses it...
Step 3: Verify ownership
After you’ve submitted your RSS feed, review the email address used to
verify ownership of your podcast. To verify that you own the podcast
content you’re adding, you need to have an email address in the
<googleplay:email> or <itunes:email> field of your podcast’s RSS feed.
Click Send verification code. Check the email account listed for your
verification email. Visit the link included in the email to complete
the verification process.
I am doing work for a non profit with 0 budget for IT. They need to allow users to enter information on a Google Form and then collect payment. I have done a lot of research on the topic and currently appears you can only add a hyperlink on the Google Forms to link to PayPal. However, I was wondering if there was some way to link the PayPal Express Checkout javascript(https://developer.paypal.com/docs/integration/direct/express-checkout/integration-jsv4/add-paypal-button/) into the Google Form so it calls back with a transaction id and status. Then I would be able to somehow insert those values into the Google Form. Any thoughts on how to integrate would be helpful. I am a developer but not familiar with Google Forms.
I recently wrestled with this exact question and ended up building a G Suite addon to make this easier for others. Coincidentally I also do volunteer IT for a small nonprofit and we wanted to use PayPal with our signup form (there's pricing for the addon but just ping me if you're a small nonprofit).
Here's what I learned while building it:
There's no way for Apps Script to modify the form once it's shown to the user, or to use Apps Script to respond to user input
There's no way to redirect the user automatically to PayPal after a form is submitted
That means if you want to send someone to PayPal, you've got to use an ordinary link. You can do this within the form by adding the URL to a question description, or you can add the URL to the text shown once someone has submitted the form. For PayPal, you've got two options for this kind of link:
PayPal buttons
Express checkout
PayPal buttons are a static link managed by PayPal. They don't require any coding - just go here and create a button. Then you need to get the raw text link for the button, which PayPal calls the "email" version. You can insert that into your form directly and tell users to access it. The one problem is there's no real way to get the transaction ID. You could try correlating the form submit time with the payment time, or the payer email with the form submit email. It's possible that neither of them will match up and you'll have to do it manually.
Express checkout requires you to dynamically create a new link for each payment by calling the PayPal API. That means your link needs to open a page that then generates an express checkout URL and redirects the user to it. You can do this using a web app in Google Apps Script using a doGet() trigger, or you can create your backend on your server in any language.
If you can run your own server somewhere, I recommend that (plenty of PaaS services have a free tier). It's much easier to test and debug things when you aren't using Apps Script. I used the PayPal Node SDK which works great despite being unmaintained. (Express checkout is "deprecated" by PayPal, but I'll bet it's not going away anytime soon). Their example will get you most of the way there. When the user arrives, generate a payment link and redirect them. When they finish they'll return to your server, and you can display whatever you want. For example, you can ask them to copy the transaction ID and paste it into your form.
Finally, when your form is submitted an onSubmit() trigger can be set up. There are actually two kinds of onSubmit() triggers for forms - one for the form itself, and a second for the spreadsheet linked to the form. You can register a trigger to do extra processing (e.g. look up the transaction ID), but you can't modify the response in the trigger. You can however modify the spreadsheet where the trigger gets sent, which for most cases is equivalent. For example, you could add a column to the spreadsheet with a link to the PayPal transaction based on the transaction code.
I have this site where visitors can pay for certain digital goods, after which they'll be presented with a download link. These downloads links last for a week before they die and become useless
I want to allow users to purchase items without having to create an account first, but just by supplying the payment details and email. I figured I could send the download link to their email once paid, but this is kind of problematic if they accidentally specific an incorrect email when paying.
Any suggestions on how best to accomplish this?
I've made such a purchase on a site called WrapBootstrap (https://wrapbootstrap.com/theme/flatboard-angularjs-admin-frontend-WB0G434G7). It integrates with PayPal in that they are navigated to PayPal, pay, and when they return, PayPal notified the site the payment was successful and then WrapBootstrap displays the download link.
I liked how seamless it was but what I found was if I ever wanted to download an item again, I didn't have a personal record of it (either in email or account). One drawback from a non-account perspective. Check it out and let me know if that answers your question.