Transitioning from Development to Production

**Important please read**  The following steps will guide you towards access to your client’s production servers once you’ve completed your development and testing.   

1. Using the template on the next page, please have your client contact Brink Support to request access for you and have the location token(s) sent. 

2. Upon receiving written approval from our mutual customer in the step above, the Brink Support Team will add your group to the client’s API location and send you the following information:  

**Important, the process is handled by our main Brink Support team, not API Support.** 

1. A new URL pointing to the client’s production environment 

2. The location token(s) for each location in that environment for that requesting customer. 

Request Template 

The following template should be used by your client whenever you require access to their production environment. Please note, that the request MUST come from the client in writing.  Customers should email their requests to BrinkAPITokenRequest@partech.com  

Subject: 

<<Customer Name>> – Location Token Request for <<Integration Partner Name>> 

Body: 

Tech Support, 

I <<First & Last Name>>, as an authorized representative of <<Company Name>>, authorize <<Integration Partner Name>> API access to the locations listed below and ParTech to issue locations tokens and access information on our behalf. 

<<List Stores Here>> 

Thank you, 

<<Customer Name>> 

PAR Status Page 

PAR has implemented the PAR Status Page to keep you informed about production related incidents, updates and schedules upgrades or maintenance. 

• Incident: Generally, these are unplanned situations where functionality severely impacts the use of our products or services.  The situation may cause interruptions in some aspects of the merchants operations.  Examples would include but are not limited to; 

  • A critical capability is unavailable 

  • System Outage 

• Scheduled Maintenance: Planned and scheduled event. Typically, a scheduled maintenance event is associated with an improvement to the system (i.e. operating system, infrastructure, etc.), that is used in support of running our applications. 

• Planned Updates: Planned and scheduled event. Associated with introducing a new version of an application (i.e. Brink 5.0a, Brink 5.0c). Generally, it is our intent to provide the initial update notification approximately 30 days in advance of deployment. 

• Deployment Update: Planned and scheduled event. This is the follow up notification of the “Planned Update” confirming the deployment date and additional details of the update. Generally, it is our intent to provide this notification approximately 7 days in advance of deploying the update. 

Visit https://status.brinkpos.net/ to subscribe.