Source Code Options

Discuss Source Code Options for Your POS Project

Review whether source-code access, modification rights and delivery conditions fit your project, with the scope defined by agreement.

Discuss Source Code Options for Your POS Project
Source Code Fit
Access and Modification Rights
Deployment Context
Development Responsibilities
Scope
Source Code Access
Rights
Use and Modification Rights
Roles
Development and Maintenance Roles
Terms
Delivery Conditions
Source Code Value

With the Source Code, You Can Do So Much More

Not just getting a copy of code. You gain ultimate control of the system. No limits from here on

Source Code Fit

Consider whether source-code access is suitable for your product model, technical team and business plans

Access and Modification Rights

Discuss the level of access and modification rights available for the specific cooperation arrangement

Deployment Context

Review how the intended operating environment may affect source-code use and project implementation

Development Responsibilities

Separate the responsibilities for development, testing, updates and technical decisions within the project

Handover Requirements

Identify the materials, access arrangements and handover items to be discussed for the project

Agreement Scope

Confirm permitted use, modification, support and delivery conditions through project discussion and contract terms

Source Code Use Cases

When Source Code Access Adds Practical Value

Source-code cooperation may be relevant for POS providers with an established technical team, a product roadmap, or a need to review and adapt selected parts of a system. The suitable scope depends on the project

  • In-house technical capability
  • A defined product roadmap
  • Selected code access or modification needs
  • Project-specific scope discussion
In-house technical capability
A defined product roadmap
Selected code access or modification needs
Project-specific scope discussion
Delivery and Development Boundaries

Make Every Technical Responsibility Clear

Before any source-code arrangement is confirmed, both sides should discuss access methods, modification work, testing, documentation, ongoing support and the conditions for delivery

  • Access and usage conditions
  • Modification and testing responsibilities
  • Documentation and handover items
  • Support and update arrangements
Access and usage conditions
Modification and testing responsibilities
Documentation and handover items
Support and update arrangements
Why Discuss Source Code With Us

Build a More Informed Source Code Plan

01

Fit the Discussion to Your Technical Team

Review what your team needs to access, modify, test or maintain before defining the cooperation scope

02

Separate Development Work From Delivery Terms

Keep technical work, handover items and contractual delivery conditions clear during project discussions

03

Discuss the Scope Before Commitmen

Source-code access, modification rights, support and future arrangements are discussed according to the specific project and agreement

Have a Source Code Requirement?

Share your technical plans and intended use case to discuss a suitable source-code arrangement