NoFraud Is Now Wyllo: What Shopify Merchants Should Recheck

Recheck the app identity, support route and contracted product scope when reviewing NoFraud under the Wyllo name. On 6 September 2026, the NoFraud homepage redirected to Wyllo’s official site. That verifies the observed public brand transition; it does not establish that every existing merchant must migrate, reinstall an app or accept new terms. NoFraud’s current redirect

Treat the change as a reason to reconcile your records with the provider, not as evidence that your current configuration stopped working. Existing customers and new buyers have different questions to answer.

Verify the account and app identity

For an existing Shopify merchant, record the installed app’s current name, developer identity, account reference and support link. Compare those details with official provider communications and the current account portal. Do not rely solely on a search result or an unfamiliar email announcing a change.

Confirm which legal entity appears on the contract and invoices. A public brand can change while the contracting entity or product entitlement remains the same. It can also accompany a substantive commercial change, but that must be established from the actual notice or agreement.

Use the provider’s official route to verify any requested credential, billing or access change. Do not send secrets to a contact merely because it uses the new brand name. A normal account-support inquiry can establish whether the request is genuine and applicable.

For a new buyer, ask which current Shopify app and onboarding path correspond to the specific product being purchased. Avoid installing an additional app simply because its name looks newer than an existing one.

Separate the public platform from your purchased scope

Wyllo’s current site presents Payment Fraud Protection, Chargeback Management and several other fraud- and abuse-related product areas. The presence of those areas does not mean an existing NoFraud contract automatically includes them. Wyllo’s product overview

List the functions your store currently uses: order assessment, a contractual guarantee, dispute preparation, reporting or another service. Then ask the provider to confirm which functions remain included, which are optional and which require a new agreement.

Pay particular attention to action authority. A broader platform may describe cancellations, customer-service recommendations or recovery workflows, but the merchant’s active settings and contract determine what can happen in its account.

If the merchant has a guarantee, obtain confirmation of the terms applying to previously approved orders and future orders. Do not infer a coverage change from a new website headline, and do not assume the old terms govern indefinitely without checking the relevant notice.

Use a transition-verification worksheet

Mark “no action required” when the provider confirms it. A rebrand should not generate unnecessary operational work. Conversely, if a real change is required, record its deadline, owner and completion evidence.

A hypothetical existing-customer review

A hypothetical merchant has an installed NoFraud-related app and several orders awaiting review. A team member sees the Wyllo site and assumes the store must uninstall the old app and install a new one immediately.

The operations lead pauses that assumption and checks the official account route. The provider confirms the merchant’s current configuration and explains whether any action is required. The team preserves open-order and dispute ownership while following only the confirmed instructions.

The merchant also asks whether a newly advertised chargeback-management function is included in its existing plan. The answer may be yes, optional or unavailable for that configuration. The team records the actual entitlement rather than enabling new permissions based on the broader platform description.

This hypothetical does not claim that Wyllo requires or avoids a specific migration. It demonstrates the evidence needed to make the transition decision safely and efficiently.

Update internal records after confirmation

Once verified, update the vendor register, support contacts, billing references and operating instructions. Preserve historical names as aliases so staff can find old invoices, approvals and case records. Do not rename source documents in a way that obscures the entity or product shown when they were issued.

If the provider requires a technical change, coordinate it with the owner of the affected workflow. Confirm how open orders, pending claims and historical records will remain accessible. Use a controlled verification of the actual account state rather than assuming a successful installation means every service is active.

For a new purchase, evaluate the current Wyllo offer on its documented scope, data requirements, authority and commercial terms. Do not use old NoFraud reviews or historical pricing as a substitute for the current proposal.

Lower Chargeback’s Provider Hub can help track current provider identity and access requirements alongside other services the merchant uses. It does not establish that a particular connection or entitlement is enabled for the account. Lower Chargeback Provider Hub

The practical goal is continuity with verified scope. Know which app and account you use, who supports it, which contract applies and whether any actual change is required. The public name transition is confirmed; the merchant’s next action should come from its own documented provider relationship.

Review provider information against your current Shopify app and agreement.

Check provider details

Related reading in this collection:

• A Chargeback Software Demo Script That Tests Real Merchant Requirements
• Adyen Disputes API or Customer Area: Plan a Shopify Merchant's Access
• Use the Product Listing from the Purchase Date in Chargeback Evidence