MICROCHIP CONNECT
TERMS & CONDITIONS
Terms governing use of the Microchip Connect platform
Effective date: 8 September 2026
Microchip Connect is a software platform operated by:
Why Go Digital Ltd
Company Registration Number: 09085173
Registered Office:
1 Brookside
Orwell
Royston
Hertfordshire
SG8 5TQ
United Kingdom
Email:
admin@whygodigital.co.uk
Microchip Connect is not a separate incorporated company and does not currently operate a public website.
1. ABOUT THESE TERMS
These Terms & Conditions govern access to and use of Microchip Connect, a software and technology platform operated by Why Go Digital Ltd.
These Terms apply, as relevant, to:
- Microchip Companies
- Microchip Databases
- Microchip Suppliers
- Veterinary Practices
- authorised users
- connected systems
- integration partners
- and other organisations authorised to use Microchip Connect.
By activating or using a Microchip Connect account, API, integration, application or related service, the participating organisation agrees to comply with these Terms together with any separate commercial agreement, pricing schedule, data-processing agreement or other written agreement entered into with Why Go Digital Ltd.
Where a separate written commercial agreement conflicts with these Terms, the terms of that agreement will prevail to the extent of the conflict.
2. MICROCHIP CONNECT SERVICE
Microchip Connect is designed to connect:
MICROCHIP SUPPLY ↓ VETERINARY PRACTICE ALLOCATION ↓ MICROCHIP IMPLANTATION ↓ REGISTRATION INFORMATION ↓ MICROCHIP DATABASE REGISTRATION
through automated digital workflows.
The service may include:
- Microchip Company accounts
- Veterinary Practice accounts
- Microchip allocation APIs
- Veterinary Practice applications
- practice identification and matching
- Master Microchip Inventory functionality
- individual microchip provenance
- Registration Transactions
- database connectors
- registration status tracking
- customer acceptance workflows
- Smart Tag pairing to individual microchips
- Smart Tag activation decision workflows (accept, decline or defer) and notification of those decisions to the relevant Microchip Database
- reporting
- reconciliation
- audit information
- integration monitoring
- and Usage-Based Pricing.
Where a Smart Tag has been pre-paired to an individual microchip before supply, the Smart Tag follows the microchip’s recorded allocation to the same Microchip Database. The Veterinary Practice is not required to scan the Smart Tag, enter a QR code or perform any additional Smart Tag process. After the microchip registration is completed, the customer may be offered the paired Smart Tag and may choose to activate it, decline it or decide later; Microchip Connect records the decision and notifies the relevant Microchip Database. Smart Tag subscription or payment setup, where required, is handled by the Microchip Database and not collected through Microchip Connect.
The exact functionality available to an organisation may depend upon its account type, integration, commercial agreement and connected systems.
3. ACCOUNTS AND AUTHORISED USERS
Users and organisations must provide accurate information when creating, activating or maintaining a Microchip Connect account.
Account information must be kept reasonably up to date.
Access to Microchip Connect is restricted to authorised users and authorised systems.
Account credentials must not be:
- shared with unauthorised persons;
- disclosed publicly;
- used to access another organisation's account;
- or used for purposes outside the authorised Microchip Connect service.
Why Go Digital Ltd may suspend or restrict access where reasonably necessary because of:
- security concerns;
- suspected misuse;
- unlawful activity;
- breach of these Terms;
- non-payment where applicable;
- technical risk;
- or protection of Microchip Connect, participating organisations, customers or other users.
4. VETERINARY PRACTICE ACCOUNT NUMBERS
Every Veterinary Practice within Microchip Connect is allocated a unique six-character Practice Account Number.
The existing format is:
THREE LETTERS + THREE NUMBERS
Examples:
- ALL001
- BRI001
- DUN001
The Practice Account Number is the principal business identifier for the Veterinary Practice throughout Microchip Connect.
Practice names, addresses, postcodes, email addresses and telephone numbers may be used for identification, search or verification but do not replace the Practice Account Number once it has been established.
Existing Practice Account Numbers must not automatically be changed or regenerated merely because a practice changes:
- name;
- address;
- postcode;
- email;
- telephone number;
- ownership;
- veterinary personnel;
- or other contact information.
Where different practice locations are represented by separate Microchip Connect practice records, each location may have its own Practice Account Number.
The Practice Account Number may be used across:
- supplier allocations;
- supplier/practice mappings;
- Master Microchip Inventory records;
- Veterinary Practice applications;
- Registration Transactions;
- database routing;
- reporting;
- audit records;
- and other Microchip Connect functions.
5. MICROCHIP COMPANY ACCOUNTS
A Microchip Company account may represent an organisation that:
- supplies microchips;
- operates a Microchip Database;
- or performs both functions.
Each Microchip Company account is treated as a separate organisational tenant.
An organisation must not access another company's restricted:
- commercial information;
- microchip allocation information;
- registration information;
- technical information;
- account information;
- integration information;
- or other confidential information
unless such access has been specifically authorised.
6. ACCOUNT ACTIVATION
Why Go Digital Ltd may issue:
- an Account Number; and
- an Activation Key
to activate a Microchip Connect account.
Activation Keys are intended for initial account activation.
An Activation Key may be:
- time limited;
- single use;
- invalidated following successful activation;
- or replaced where reasonably required.
Activation Keys must not be used as permanent API credentials.
After activation, separate machine-to-machine integration credentials may be issued for APIs and other connected systems.
7. SUPPLIER ALLOCATION AUTOMATION
Microchip Connect is intended to operate automatically with a participating Microchip Supplier's existing:
- stock system;
- order system;
- sales system;
- dispatch system;
- or other authorised business software.
The supplier may transmit information including:
- complete individual microchip numbers;
- batch information;
- microchip ranges;
- supplier order references;
- dispatch references;
- Practice Account Number where known;
- Veterinary Practice details where required;
- allocation date;
- dispatch date;
- and associated Microchip Database information.
Normal supplier operation should not require staff to manually re-enter each microchip allocation into Microchip Connect.
Microchip Connect is designed to operate in the background as part of the supplier's normal order and dispatch process.
8. PRACTICE IDENTIFICATION AND MATCHING
Where a valid Practice Account Number is supplied, Microchip Connect will use that number as the primary Veterinary Practice identifier.
Where the Practice Account Number is not known, Microchip Connect may:
- check an existing supplier/customer mapping;
- search existing Veterinary Practice records using supporting information such as:
- Practice Name;
- Postcode;
- Address;
- Email;
- Telephone;
- identify the relevant existing Practice Account Number.
Where a reliable match cannot be established, Microchip Connect may place the allocation into an exception state rather than:
- guess;
- select an uncertain practice;
- or automatically create a duplicate Veterinary Practice.
Once a supplier customer reference has been reliably mapped to a Practice Account Number, that mapping may be reused for future allocations.
9. MICROCHIP PROVENANCE AND ASSOCIATED DATABASE
Microchip Connect is designed to maintain the relationship between:
THE INDIVIDUAL MICROCHIP ↓ THE COMPANY THAT SUPPLIED IT ↓ THE VETERINARY PRACTICE RECEIVING IT ↓ THE ASSOCIATED MICROCHIP DATABASE
The complete individual microchip number and its recorded supply allocation are the principal provenance information.
Microchip prefixes and ranges may be used as supplementary information but should not automatically determine the registration destination.
Microchip Connect must not be treated as independently choosing a Microchip Database according to its own commercial preference.
Where an associated database relationship has been established, Microchip Connect follows the recorded supply provenance and looks to register the microchip first with the database associated with that allocation, subject to:
- the applicable registration workflow;
- database availability;
- customer requirements;
- contractual arrangements;
- and any authorised alternative registration route.
10. VETERINARY REGISTRATION WORKFLOW
When a Veterinary Practice implants a microchip, Microchip Connect may receive information required for registration.
This may include:
KEEPER / CUSTOMER INFORMATION
- name;
- address;
- postcode;
- email;
- telephone number;
- and other information required by the destination database.
PET INFORMATION
- pet name;
- species;
- breed;
- sex;
- date of birth or age;
- colour;
- and other relevant registration information.
MICROCHIP INFORMATION
- complete microchip number;
- batch information where relevant;
- and related identification information.
IMPLANTATION INFORMATION
- implantation date;
- Veterinary Practice;
- implanter details where required;
- and relevant implantation information.
PRACTICE INFORMATION
The Practice Account Number identifies the Veterinary Practice associated with the registration workflow.
Microchip Connect may combine this registration information with the existing microchip supply and allocation information and create a Registration Transaction.
11. DATABASE CONNECTORS AND DATA TRANSFORMATION
Different Microchip Databases may require different:
- data fields;
- registration formats;
- APIs;
- authentication methods;
- validation requirements;
- account creation processes;
- customer acceptance requirements;
- and technical interfaces.
Microchip Connect may maintain a common registration dataset and transform that dataset into the format required by the relevant participating Microchip Database.
Participating organisations are responsible for providing accurate technical integration specifications and maintaining their systems so that authorised registration information can be transmitted and received.
11A. INTEGRATION ACCESS AND PERMISSIONS
For Microchip Connect APIs and integrations to function, participating Microchip Suppliers and participating Microchip Databases must provide Why Go Digital Ltd with the access, permissions and technical cooperation reasonably required to connect Microchip Connect to their authorised systems.
This may include, where applicable:
- API endpoints;
- API credentials;
- integration credentials;
- authentication requirements;
- technical documentation;
- data-field specifications;
- request and response formats;
- registration rules;
- webhook or callback configuration;
- test or sandbox environments;
- sample data;
- error and status codes;
- connection configuration;
- and other technical information reasonably necessary to develop, test, operate, support and maintain the authorised integration.
For a Microchip Supplier, this may include authorised access to or integration with the supplier's:
- stock software;
- order software;
- sales software;
- allocation software;
- dispatch software;
- or other relevant system
so that information concerning microchips supplied to Veterinary Practices can be transmitted automatically to Microchip Connect.
For a participating Microchip Database, this may include authorised access to or integration with the database's registration system or technical interface so that Microchip Connect can:
- transmit registration information;
- receive validation responses;
- receive registration status;
- support customer acceptance;
- receive registration confirmation;
- and perform other agreed registration functions.
The participating organisation confirms that it has the authority to provide such access, permissions, credentials and technical information.
The participating organisation must obtain any internal approvals or third-party permissions necessary for the integration.
Why Go Digital Ltd will use the access provided only for purposes reasonably required to:
- provide the authorised Microchip Connect integration;
- test the integration;
- maintain the connection;
- provide technical support;
- troubleshoot faults;
- maintain security;
- and operate the agreed Microchip Connect functionality.
Microchip Connect does not require unrestricted access to unrelated systems, unrelated data or functionality outside the authorised integration.
If required access, permissions, credentials, documentation or technical cooperation are:
- withdrawn;
- unavailable;
- expired;
- materially altered;
- disabled;
- or restricted,
some or all Microchip Connect functionality may become unavailable until the connection has been restored or updated.
11B. AUTHORISED SYSTEM ACCESS
All access by Microchip Connect to third-party systems must be authorised.
Microchip Connect must not be used to bypass security controls or access systems without permission.
Where Microchip Connect connects to a participating supplier or database, the connection is made with the authority of that organisation and for the defined purpose of providing the Microchip Connect service.
Any software, connector, API credential, system permission or other integration method provided to Why Go Digital Ltd must only be used within the authorised scope.
11C. MICROCHIP SUPPLIER INTEGRATION
Participating Microchip Suppliers agree to provide the information reasonably required to establish the supply provenance of microchips supplied to Veterinary Practices.
This may include:
- complete individual microchip numbers;
- batch or range information;
- supplier order reference;
- dispatch reference;
- Veterinary Practice details;
- Practice Account Number where known;
- allocation date;
- dispatch date;
- associated Microchip Database;
- and other information reasonably required for the authorised Microchip Connect workflow.
The preferred process is automated electronic transmission from the supplier's existing systems.
The supplier should not normally be required to manually re-enter this information into Microchip Connect.
11D. MICROCHIP DATABASE INTEGRATION
Participating Microchip Databases agree to provide the technical information reasonably required for Microchip Connect to submit and manage registrations through the database's authorised interface.
This may include:
- registration API access;
- authentication requirements;
- registration field definitions;
- validation rules;
- keeper/customer acceptance requirements;
- request formats;
- response formats;
- account creation requirements;
- existing-account lookup requirements;
- registration status information;
- error codes;
- and registration confirmation information.
The participating Microchip Database remains responsible for determining whether a registration satisfies its own:
- legal requirements;
- technical requirements;
- administrative requirements;
- customer terms;
- privacy requirements;
- and registration rules.
The participating Microchip Database remains responsible for maintaining the final registration record.
11E. CUSTOMER ACCEPTANCE WORKFLOWS
Where a participating Microchip Database requires a keeper/customer to:
- accept;
- confirm;
- approve;
- activate;
- or otherwise complete
a microchip registration, Microchip Connect may provide or support the software workflow required to facilitate that process.
The participating Microchip Database remains responsible for defining:
- acceptance wording;
- terms and conditions;
- privacy information;
- account creation requirements;
- customer communications;
- registration requirements;
- and the legal consequences of acceptance, refusal or failure to complete the registration.
Microchip Connect may record the status of the customer acceptance process for:
- operational purposes;
- audit purposes;
- registration status;
- troubleshooting;
- and reconciliation.
Customer acceptance of a microchip registration must not automatically be treated as consent to receive marketing communications.
12. CUSTOMER ACCEPTANCE
Where a destination Microchip Database requires keeper acceptance, confirmation, terms acceptance or another customer action, Microchip Connect may support the software workflow used to request and record that action.
Where supported, this may allow the registration process to progress while the owner is still at the Veterinary Practice.
The destination Microchip Database remains responsible for its own:
- terms;
- privacy information;
- acceptance requirements;
- customer communications;
- account creation rules;
- and registration completion requirements.
Not every Microchip Database is required to use the same customer acceptance workflow.
13. DESTINATION DATABASE RESPONSIBILITY
Microchip Connect facilitates:
- data transmission;
- workflow automation;
- registration processing;
- technical status;
- and reconciliation.
Microchip Connect does not replace the legal, technical or administrative responsibilities of a participating Microchip Database.
The destination Microchip Database remains responsible for:
- deciding whether the registration meets its requirements;
- maintaining the ultimate registration record;
- customer account management;
- database compliance;
- privacy information;
- registration terms;
- and any statutory or regulatory obligations applying to the database.
14. FAILED, PENDING AND UNRESOLVED REGISTRATIONS
If a registration cannot be completed immediately, Microchip Connect may retain the Registration Transaction with an appropriate status.
Possible statuses may include:
- pending;
- queued;
- submitted;
- customer action required;
- customer declined;
- failed;
- rejected;
- unresolved;
- manual review;
- or another relevant status.
Microchip Connect may retry eligible technical failures.
Exceptions may be surfaced to authorised users for investigation.
A failed or unresolved registration must not be treated as successfully completed merely because data was transmitted.
15. RETURNS, REALLOCATIONS AND ALLOCATION HISTORY
Microchip Connect may support:
- returned microchips;
- cancelled allocations;
- reallocations;
- and changes to supply allocation.
Important provenance information should not be silently overwritten.
Where an allocation changes, Microchip Connect may retain:
- the previous allocation;
- the date of the change;
- the new allocation;
- the party or system making the change;
- and other relevant audit information.
16. REGISTRATION TRANSACTIONS
The principal commercial unit of usage for Microchip Connect is a:
REGISTRATION TRANSACTION
A Registration Transaction represents the processing of an individual microchip registration through Microchip Connect.
Multiple technical:
- API requests;
- responses;
- retries;
- callbacks;
- status checks;
- customer acceptance updates;
- or confirmation messages
associated with the same registration do not, by themselves, create multiple Registration Transactions.
One microchip registration should normally correspond to one Registration Transaction for commercial measurement purposes.
17. USAGE-BASED PRICING
Microchip Connect uses:
USAGE-BASED PRICING
Charges are based on:
REGISTRATION TRANSACTIONS
or another commercial unit specifically agreed in writing with the customer.
Charges are not based simply on the raw number of technical API calls.
The applicable:
- transaction rate;
- billing milestone;
- volume pricing;
- minimum charge;
- enterprise rate;
- or other commercial arrangement
will be set out in the relevant:
- commercial agreement;
- pricing schedule;
- order;
- or other written agreement.
Different participating organisations may have different commercial terms.
18. BILLING AND PAYMENT
Where charges apply, Why Go Digital Ltd may record billable Registration Transactions and issue:
- invoices;
- usage statements;
- transaction statements;
- or other billing records
in accordance with the relevant commercial agreement.
Technical retries must not create duplicate charges for the same Registration Transaction.
Payment terms, VAT, billing periods, credits, disputes, minimum payments and other financial provisions will be governed by the applicable commercial agreement or invoice terms.
19. API AND INTEGRATION USE
API and integration credentials are confidential.
They must only be used for authorised Microchip Connect purposes.
Connected organisations must not:
- access another organisation's restricted data;
- attempt to bypass security controls;
- misuse credentials;
- interfere with Microchip Connect systems;
- inject malicious software or code;
- deliberately overload the service;
- reverse engineer protected components except where legally permitted;
- or use the integration for unauthorised purposes.
Why Go Digital Ltd may:
- revoke credentials;
- suspend credentials;
- rotate credentials;
- or require credentials to be replaced
where reasonably necessary for security or operational reasons.
20. DATA ACCURACY AND PARTICIPATING ORGANISATION RESPONSIBILITIES
Participating organisations are responsible for the accuracy and lawfulness of information they submit to Microchip Connect.
Why Go Digital Ltd may validate:
- data format;
- microchip identifiers;
- account relationships;
- Practice Account Numbers;
- required fields;
- duplicate events;
- and other information.
However, Why Go Digital Ltd is not responsible for errors originating from inaccurate information supplied by:
- Veterinary Practices;
- Microchip Suppliers;
- Microchip Databases;
- connected systems;
- keepers/customers;
- or other third parties.
Participating organisations are responsible for maintaining their own systems and notifying Why Go Digital Ltd of material technical changes that may affect the integration.
21. SECURITY
Participating organisations must take reasonable steps to protect:
- user accounts;
- devices;
- connected systems;
- API credentials;
- activation credentials;
- and other security information.
Why Go Digital Ltd may apply security controls including, where implemented:
- authentication;
- role-based access;
- tenant separation;
- credential controls;
- audit logging;
- transaction identifiers;
- duplicate protection;
- retry controls;
- exception handling;
- and other technical or organisational safeguards.
No electronic service can be guaranteed to be:
- uninterrupted;
- completely error-free;
- or entirely immune from security risks.
22. SERVICE AVAILABILITY AND CHANGES
Why Go Digital Ltd may:
- maintain;
- modify;
- update;
- improve;
- replace;
- or develop
Microchip Connect from time to time.
Access may temporarily be restricted where reasonably required for:
- maintenance;
- security;
- upgrades;
- technical changes;
- emergency work;
- or service continuity.
Why Go Digital Ltd does not guarantee uninterrupted availability unless a separate written Service Level Agreement expressly provides otherwise.
Why Go Digital Ltd will not be responsible for failure or delay caused by matters outside its reasonable control, including:
- unavailable third-party systems;
- changes to third-party APIs;
- invalid or withdrawn credentials;
- failures of supplier systems;
- failures of Microchip Databases;
- PMS failures;
- internet connectivity;
- hosting or infrastructure failures outside its control;
- incomplete technical documentation;
- or participating organisations failing to provide required integration access or cooperation.
23. INTELLECTUAL PROPERTY
Microchip Connect and its associated:
- software;
- APIs;
- source code;
- workflows;
- database structures;
- interfaces;
- designs;
- documentation;
- branding;
- know-how;
- algorithms;
- technical processes;
- and related intellectual property
are owned by or licensed to Why Go Digital Ltd unless expressly stated otherwise.
Access to or use of Microchip Connect does not transfer ownership of any intellectual property rights to a participating organisation.
No participating organisation may copy, reproduce, distribute, disclose or commercially exploit protected Microchip Connect technology except as expressly authorised in writing.
24. CONFIDENTIALITY
Each participating organisation must protect non-public:
- technical information;
- commercial information;
- operational information;
- pricing;
- API information;
- credentials;
- integration specifications;
- and other confidential information
received through its relationship with Microchip Connect.
Confidential information must only be used for authorised purposes.
These obligations do not apply to information that:
- is already lawfully public;
- was independently developed without use of confidential information;
- was lawfully obtained from another source;
- or must be disclosed by law.
25. SUSPENSION AND TERMINATION
Why Go Digital Ltd may suspend or terminate access where reasonably required because of:
- material breach;
- security risk;
- misuse;
- unlawful activity;
- non-payment;
- repeated technical abuse;
- unauthorised access;
- or material risk to Microchip Connect or another participant.
Following termination or suspension:
- user access may be disabled;
- integration credentials may be revoked;
- APIs may become unavailable;
- and other connected functionality may cease.
Rights and obligations intended to survive termination will continue, including where applicable:
- confidentiality;
- intellectual property;
- accrued payment obligations;
- audit records;
- legal records;
- and data-protection obligations.
26. LIABILITY
Nothing in these Terms excludes or limits liability where such liability cannot lawfully be excluded or limited.
Subject to any separate written agreement, Why Go Digital Ltd is not responsible for losses caused by:
- inaccurate information supplied by third parties;
- Veterinary Practice system failures;
- supplier software failures;
- Microchip Database failures;
- PMS failures;
- third-party API changes;
- network failures;
- internet connectivity;
- unauthorised alteration of third-party systems;
- withdrawal of required integration access;
- or other external services outside Why Go Digital Ltd's reasonable control.
Specific:
- financial liability caps;
- exclusions;
- indemnities;
- service credits;
- and other liability provisions
may be set out in a separate commercial agreement.
27. DATA PROTECTION
Personal information processed through Microchip Connect is handled in accordance with:
- the Microchip Connect Privacy Policy;
- applicable UK data-protection legislation;
- and relevant contractual arrangements.
Depending on the processing activity, Why Go Digital Ltd may act as a:
- Data Controller; or
- Data Processor.
Participating Veterinary Practices, Microchip Databases, suppliers and other organisations may also have their own data-protection responsibilities.
Where required, participating organisations must enter into appropriate:
- Data Processing Agreements;
- data-sharing arrangements;
- or other contractual privacy arrangements
with Why Go Digital Ltd.
Acceptance of a microchip registration must not automatically be treated as marketing consent.
28. GOVERNING LAW
These Terms are governed by the laws of England and Wales unless a separate written agreement specifies otherwise.
The courts of England and Wales will have jurisdiction, subject to any alternative dispute-resolution or jurisdiction provisions contained in a separate written agreement.
29. CHANGES TO THESE TERMS
Why Go Digital Ltd may update these Terms as Microchip Connect develops.
Changes may be required because of:
- new functionality;
- integrations;
- technical development;
- regulatory changes;
- security requirements;
- or changes to the Microchip Connect commercial model.
Material changes affecting an existing commercial customer should be communicated in accordance with the applicable commercial agreement.
30. CONTACT
Microchip Connect is operated by:
Why Go Digital Ltd
Company Registration Number: 09085173
Registered Office:
1 Brookside
Orwell
Royston
Hertfordshire
SG8 5TQ
United Kingdom
Email:
admin@whygodigital.co.uk
Microchip Connect does not currently operate a public website.
