Questions about shops, payments and apps

Create an offer in JustPayFor and share a payment link, basket or QR code. Your customer opens the offer and pays through your provider. A full shop suits a larger browsable catalogue and a more involved ordering process.

A payment link takes a customer to payment for an agreed offer. A basket presents multiple products or services together. Choose according to whether the customer is paying for one agreed item or a set of items.

Show a QR code that opens the offer, on a screen or printed material. The customer opens it on their phone and selects an available payment method. This is an online payment rather than a contactless card transaction on a terminal.

Yes. Create a payment for the agreed service or booking and share the link. Explain booking and cancellation terms before payment. Taking a payment does not replace the agreement with the seller.

Yes. The platform covers events and tickets as well as online fundraisers. A fundraising organiser must meet the payment partner’s requirements. Prepare the purpose and organiser details; do not assume every personal fundraiser will be accepted.

Payment processing requires setup and verification under your chosen provider’s requirements. JustPayFor does not replace the provider or its agreement. Select a provider for your market, currency and the methods available to your business.

The current JustPayFor offer has no monthly platform subscription. Payment processing fees depend on your provider’s terms. Check the current offer and your agreement before launch; no subscription does not mean no transaction costs.

Choose a shop for a large catalogue, categories, shipping, order management or process integrations. JustPayFor suits sharing specific offers and payments. We can help match the solution to your sales workflow.

Record when the error occurred, the affected page and recent changes such as an extension, upgrade or PHP version. Keep logs and a backup. Avoid reinstalling blindly or sending passwords through the form. A support request lets us agree a safe investigation scope.

Possible causes include provider notification settings, an unreachable notification endpoint or an extension conflict. Investigation needs the order reference, payment time and integration logs without card details. Checks depend on the gateway and extension version.

We plan upgrades around the OpenCart version, extensions, theme and database. A backup and test environment come first. We agree data migration, checkout tests and rollback rather than assuming every old extension is compatible.

Yes. Work can cover one fault, payment configuration, extension installation or larger shop improvements. Provide the system version and extension name. The quote depends on compatibility and the changes needed.

Check the requirements of the specific OpenCart and extension versions: PHP, database, extensions, ionCube Loader, HTTPS and backups. Log access and a test environment matter too. We can help assess the setup; our hosting partners are listed on the studio website.

ionCube Loader runs encoded PHP extensions that require it. The loader must be compatible with the extension and environment. It does not replace updates, access controls or backups and is not a security guarantee for the entire shop.

Our existing extension terms provide for a perpetual licence. This does not mean perpetual downloads, support or access to every future release. Check the licence and purchased product specification for the applicable terms.

Updates within the purchased product line and moving to a new OpenCart major version are different scopes. Downloads and updates are time-limited under the existing terms. Check your purchase conditions; a new OpenCart version may need a new extension release.

The licence is linked to the domain specified at purchase. Ask about a demo or testing terms before installing on another domain. Do not assume a test environment is automatically covered by a production licence.

Existing terms allow transfers under specified conditions. Fees and domain changes depend on support status and transfer history. Ask us to check your purchase before changing the owner or domain.

After payment, files are available in the Downloads area of your customer account in the shop. Purchase terms provide one year of file and update access for the purchased product line. A perpetual licence does not mean perpetual downloads; ask us to check options for an older purchase.

A quote covers the agreed design, features, content, integrations and implementation. Domain, hosting, licences and provider fees are agreed separately. Tell us about product types, languages, shipping and external systems; page count alone does not describe the scope.

Timing is agreed after reviewing content, design, integrations and migration. Ready-to-use text, images and timely reviews help. We agree a schedule and responsibilities on both sides before starting.

Prepare your offer, audience, content structure, logo, images and integration requirements. For a shop, include sample products, shipping, payments and languages. We agree which materials you provide and which are included in our work.

Our offer includes preparation for shop operation and post-launch support. Training scope, support duration and ongoing care are agreed for the project. You can also request individual improvements.