Version 1.0 · 21 October 2026
These iVendNext Developer Terms (the Terms) are an agreement between you and the CitiXsys company named as the party in the signed copy of these Terms you receive when you accept them (CitiXsys, we, us). Our offices are listed at ivend.com/contact-us, and legal information about CitiXsys and iVendNext is at legal.ivend.com.
1. Who these Terms are for, and accepting them
1.1 Who. These Terms apply to anyone CitiXsys admits as a builder on iVendNext: an iVendNext partner, a retailer’s own IT team, or a person building for either (you).
1.2 Acting for a company. If you accept for a company, you confirm you have authority to bind it, and "you" means both you and that company.
1.3 Accepting. You accept these Terms by signing them through the form CitiXsys sends you. CitiXsys gives no access before you have.
1.4 If you are already a CitiXsys customer. If your company holds an iVendNext customer agreement, that agreement continues to govern your company’s use of its iVendNext service. These Terms govern only what they grant below. If the two conflict on your use of the iVendNext service, the customer agreement wins.
2. Definitions
- Developer Assets: the partner kit (its guide, recipes, samples, tools, contracts, design kit and AI builder kit), the API description, the sandbox site and its API key, access to CitiXsys’s developer GitHub organisation and its feedback repository, and any other material CitiXsys provides for building on iVendNext.
- Your App: anything you build to work with iVendNext — a service you run, a till key’s service, a manifest, a sandboxed function, a payment connector, a page shown in our frame — together with its updates.
- The Four Rules: the rules every build keeps, published in the kit’s guide (chapter 3): (1) money enters the sale visibly, before payment; (2) never override or patch iVendNext; (3) your code runs on your server — inside a retailer’s site you ship data, not code; (4) your screens use our doors.
- The Library: CitiXsys’s app library, where iVendNext apps are listed for retailers.
3. What CitiXsys grants you
3.1 The kit. The partner kit is public, under the Apache License 2.0 (its LICENSE and NOTICE). These Terms add what is not public: the sandbox site, the feedback repository and the publishing pipeline, as follows.
3.2 A sandbox site. CitiXsys may give you one sandbox site, with an administrator login and an API key, to build and test Your App. It is hosted by CitiXsys, holds made-up demo data, and may be reset or removed (§6.2).
3.3 The feedback repository. You may raise questions, defects and requests through the feedback forms in the developer organisation’s private feedback repository.
3.4 Our marks, within the trademark rules (§8).
3.5 No charge. CitiXsys charges nothing for the kit, the sandbox site or the feedback repository. Listing an app in the Library is free unless CitiXsys and you agree a charge in writing; any paid listing, and paid hosting (Schedule 1), will be on separate written terms or a schedule to these Terms.
3.6 Keys. You issue access keys for your own listed apps to your customers’ sites through CitiXsys’s publishing pipeline. You never issue a key for another maker’s app.
3.7 Nothing else. These Terms grant no right in iVendNext, its source code, CitiXsys’s products or marks beyond what this section says. CitiXsys and its licensors keep all rights in them.
4. What you may not do
4.1 Keep the Four Rules. Your App keeps the Four Rules. In particular, you never write code that runs inside a retailer’s iVendNext site: inside a site you ship data (manifests, sandboxed functions) only.
4.2 No misuse. You will not: (a) try to reach any iVendNext site, account or data you were not given; (b) probe, load-test or attack iVendNext or another builder’s sandbox, except testing of your own sandbox in proportion to building Your App; (c) share your sandbox login or API key with anyone outside your team; (d) use the Developer Assets to copy iVendNext itself; (e) break the Acceptable Use Policy at legal.ivend.com.
4.3 Confidentiality. Everything CitiXsys tells you that is not public about iVendNext (its plans, its roadmap, unpublished features, other builders’ work) is confidential. You use it only to build Your App, protect it with at least reasonable care, and share it only with your own team members who need it and are bound to the same duty. This does not cover what is or becomes public without your fault, what you already knew, or what you are required by law to disclose (you tell us first where the law allows).
4.4 Security reports. You report a security weakness in iVendNext or the kit privately, as the kit’s SECURITY.md says, and never publish it before CitiXsys has had a reasonable time to fix it.
4.5 Data in a sandbox. See §6.
4.6 Laws and sanctions. You comply with the laws that apply to Your App, including data-protection, consumer and export-control laws. You are not in a country or on a list that sanctions laws bar CitiXsys from dealing with.
5. Your App is yours
5.1 Ownership. Your code, your manifests, your sandboxed functions and your data stay yours. CitiXsys claims no ownership of them. Code that only talks to iVendNext over the network is yours, and no iVendNext licence reaches it. (A sample you copied from the kit keeps its Apache-2.0 notice: you own your changes, not our sample.)
5.2 The licence you give CitiXsys. So that CitiXsys can run Your App for the retailers who install it, you grant CitiXsys a non-exclusive, worldwide, royalty-free licence to store, copy (including to tills and to backups), run, scan, test and display your manifests and sandboxed functions, and to read Your App’s listing material, for as long as they are installed on or listed for an iVendNext site, and for CitiXsys’s backup retention period after. A retailer’s right to use Your App comes from your own terms with that retailer, not from CitiXsys.
5.3 Third-party code in Your App. Your App carries a completed licence file and a list of the third-party components it bundles. You confirm Your App complies with every licence it uses, and you meet any duty those licences place on you, including any duty to offer source code. CitiXsys may refuse to list or host an app that bundles a component under a licence that would place a duty on CitiXsys (for example, the GNU Affero GPL), unless you publish that source and Your App links to it.
5.4 Your name. You allow CitiXsys to name you and show your logo as an iVendNext partner or builder, and to promote Your App, on CitiXsys’s websites and material. You may ask us to stop at any time.
5.5 Contributions to the kit. A change you propose to the kit is given under the kit’s licence (Apache-2.0) and the Developer Certificate of Origin, as the kit’s CONTRIBUTING.md says. Where you contribute for a company, the company confirms that its staff’s contributions are authorised by it and given under Apache-2.0.
5.6 Feedback. If you send CitiXsys suggestions about iVendNext or the kit, CitiXsys may use them freely, without paying you or naming you.
6. Data in a sandbox
6.1 Test data only. You put no real personal data in a sandbox site — no real shopper, employee or customer details — and no export from a real shop, no real payment credentials, and you connect no real mail, fiscal or payment service.
6.2 What CitiXsys may do. CitiXsys may inspect, reset or delete a sandbox site at any time, without notice where it holds data this section forbids. Sandbox sites are hosted in the United States and are not backed up for you: keep your work in your own repository.
6.3 Who is responsible. CitiXsys handles your own account details (your name, email and GitHub username) under its privacy policy at legal.ivend.com. Any personal data you put in a sandbox against §6.1 is your responsibility.
6.4 No staging copies. CitiXsys does not give builders copies of a retailer’s live data.
7. CitiXsys may change the platform
7.1 Versions. Until iVendNext POS’s general release, an extension point’s contract, an API call the kit describes or the manifest format may change, with notice in the kit’s changelog. From the general release, each version is served for 12 months after its successor ships (the kit’s guide, chapter 18). Beyond that policy, CitiXsys promises no compatibility.
7.2 No support duty. CitiXsys helps builders through the feedback forms, but has no duty to support you, Your App or your customers, or to fix a defect by any date.
8. The iVendNext name and marks
8.1 The marks. "iVendNext", "iVend", "CitiXsys" and their logos are trademarks of CitiXsys. The kit’s Apache-2.0 licence grants no right to them.
8.2 What you may say. "Built for iVendNext", "works with iVendNext", "an iVendNext Partner" (once CitiXsys has accepted you as one), and the partner badge CitiXsys supplies, unaltered.
8.3 App names. "⟨Name⟩ for iVendNext" is allowed. A name that begins with or is built on our marks ("iVendNext ⟨Name⟩", "iVendX") is not.
8.4 Domains and accounts. You register no domain name, social-media handle or app-store name that contains our marks or something confusingly similar. If you have, you transfer it to CitiXsys on request, at no charge.
8.5 No endorsement. You do not suggest that CitiXsys made, certified, endorsed or guarantees Your App, beyond a certification CitiXsys actually granted.
8.6 Stop on request. You promptly stop any use of our marks CitiXsys asks you to stop. Goodwill from your use of our marks belongs to CitiXsys. Your own marks stay yours.
9. Responsibility for Your App
9.1 Yours. You are responsible for Your App, its operation and support, what it does to a retailer’s site, and your relationship with your customers, including your own terms and privacy notice for them.
9.2 Your promises. You confirm that you have the rights to everything in Your App, that it does not infringe anyone’s rights, that it carries no malicious code, and that what you tell CitiXsys and retailers about it is accurate.
9.3 Indemnity. You will defend CitiXsys against any third-party claim arising from Your App or from your breach of these Terms, and pay what a court awards or a settlement you agree requires. CitiXsys tells you of the claim promptly and lets you control the defence; you settle no claim that binds CitiXsys without CitiXsys’s consent, which it will not unreasonably withhold.
10. No warranty
The Developer Assets are provided "as is", with all faults. To the extent the law allows, CitiXsys gives no warranty of any kind, express or implied, including of merchantability, fitness for a purpose, non-infringement, or that a sandbox or service will be available, secure or error-free.
11. Limit of liability
11.1 To the extent the law allows, CitiXsys is not liable for any indirect, incidental, special or consequential loss, or for lost profits, revenue, data or goodwill.
11.2 CitiXsys’s total liability under these Terms is limited to one hundred US dollars (USD 100).
11.3 Nothing in these Terms limits liability that the law does not allow to be limited.
12. Suspension and ending
12.1 You may stop at any time by telling CitiXsys.
12.2 CitiXsys may end these Terms or any access on 30 days’ notice, for any reason. It may suspend or end access at once if you break these Terms (including the Four Rules, §6 or §8), if the law requires it, if your use could harm iVendNext, a retailer or another builder, or if CitiXsys stops the programme. Access pauses after a new version of the Terms is published until you accept it (with 30 days’ grace).
12.3 On ending, your sandbox site, API key and organisation access end; CitiXsys may delete the sandbox. Your use of the public kit under its Apache-2.0 licence is not affected. Sections 4.3, 5, 8.6, 9, 10, 11 and 14 survive.
13. Changes to these Terms
CitiXsys may publish a new version at legal.ivend.com. It tells you by email at least 30 days before the new version applies to you. You accept a new version by signing it (see the acceptance box above); if you do not, these Terms end when the 30 days run out.
14. General
14.1 Law and courts. These Terms are governed by the laws of Singapore. The courts of Singapore have exclusive jurisdiction, except that CitiXsys may seek urgent relief to protect its confidential information or marks in any court.
14.2 Whole agreement. These Terms (with any schedule that applies) are the whole agreement between you and CitiXsys about the Developer Assets.
14.3 Assignment. You may not transfer these Terms without CitiXsys’s written consent. CitiXsys may transfer them to a company in its group or in a merger or sale.
14.4 Notices. CitiXsys sends notices by email to the address you signed with, or through the developer organisation. You send notices to CitiXsys at the contact details on ivend.com/contact-us, or to the address in your signed copy.
14.5 Open-source parts. Where a Developer Asset is under an open-source licence (the kit is Apache-2.0), that licence governs it, and these Terms add only what they say.
14.6 Independent parties. Nothing here makes you CitiXsys’s agent, partner in law, employee or joint venturer.
Schedule 1 — App Hosting
Applies when CitiXsys hosts an app for a maker (a partner, or a retailer whose app CitiXsys’s Consulting Team built), under a hosting plan ordered in writing. For a retailer, this schedule attaches to its iVendNext customer agreement instead of these Terms.
- The service. CitiXsys runs the app’s container in a CitiXsys cloud account (managed containers), or operates it inside the maker’s or the retailer’s own cloud account (managed operations), on the plan ordered.
- Price and term. The plan’s monthly price, as published in the kit’s hosting chapter on the day of the order, billed monthly to whoever ordered it, as the order says (an online order is paid by card or invoice through CitiXsys’s checkout). No minimum term; either side may end a plan at the end of any month. A plan that is not paid stops at the end of the month.
- Licence to CitiXsys. The maker grants CitiXsys a non-exclusive, royalty-free licence to run, copy, store, scale, back up and scan the app, for as long as CitiXsys hosts it and for its backup retention period after.
- Who answers for what. The maker answers for what the app does, including to a retailer’s site and its data. CitiXsys answers for running the infrastructure with reasonable care. CitiXsys’s total liability under this schedule is limited to the hosting fees paid for that app in the 12 months before the claim.
- Security incidents. Each side tells the other within 24 hours of becoming aware of a security incident affecting the app or the infrastructure it runs on. CitiXsys may stop the app at once to contain an incident or protect a retailer.
- Managed operations in another party’s account. The account’s owner grants CitiXsys access through a role it can revoke at any time. The owner keeps the account, its bill and its other resources; CitiXsys acts in it only on the owner’s instructions and only for the app.
- Third-party code. §5.3 of the Terms applies to every hosted app.
- Data. The data-protection agreement already in place with the maker or retailer applies to hosted apps.
- On ending. For 30 days after a plan ends, CitiXsys returns on request what the maker supplied (the container image or its source, the settings) and the app’s data; then CitiXsys deletes them.
- A Consulting-built app run by the customer. If a retailer chooses to run an outside service CitiXsys’s Consulting Team built for it in its own cloud, CitiXsys hands over its source under the licence in the retailer’s statement of work (the Apache License 2.0). An app that runs inside the retailer’s iVendNext site is not handed over.