- Headline: ...for Shopify *stores
- CTA should be "Integrate now"
- We are completely missing the top propositions form our side - Checkout (with all its features incl. industry-leading SR, etc.). Global payments is a nice-to-have IMHO in most cases - we can make that a feature of Checkout like language support.
- Integration - instead of a video people would be impatient with, can we have a simple animated GIF since it's just a few steps now?
- May 2022
-
razorpay.com razorpay.com
-
- Feb 2022
-
betasite.razorpay.com betasite.razorpay.com
-
3. Go Live Checklist
What checklist are we talking about here? Didn't get it. A checklist should literally be a list of things to be done to go live
-
-
betasite.razorpay.com betasite.razorpay.com
-
Handy Tips
This is a not a tip. This is an important note
-
You
Number & list of hyperlinks to the various types of tests they can do
-
Test Integration
Let's maintain numbering in titles. Need navigation link back to step one here
-
-
betasite.razorpay.com betasite.razorpay.com
-
his completes your integration.
Next step should be linked here. For a regular Wix plugin merchant, this additional information can be confusing & mostly unnecessary.
-
- Jan 2022
-
betasite.razorpay.com betasite.razorpay.com
-
Subscribe to our developer updates
Am I missing something, or is this article ending abruptly? What about rest of the steps?
-
Watch the short animation
Shouldn't this come earlier in the flow? Maybe after section header. It should also contain flow from home page - will barely add 2 seconds more. A user can easily get what to do, and skip the text too
-
webhooks
- Capitalize W
- This whole sentence is a tricky one - it makes it sound like I need to do integration tech work with Webhooks. Can we just say "Your Wix plugin uses Razorpay Webhooks, and those must be enabled for your plugin to work". Also, this line should not be part of the numbered list, but a sub-text of the section header
-
development platform
it's a website builder - we should probably state that. Development platform sounds tech-heavy
-
You can integrate
We should emphasize on it being a one/few step, no-code integration
-