DOCSLIB.ORG

The Emaginepos Guide to Pax / Emv / Broadpos

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Emaginepos Guide to Pax / Emv / Broadpos THE EMAGINEPOS GUIDE TO PAX / EMV / BROADPOS Author Davis Ford <[email protected]> Last Updated 9/22/2016 THE EMAGINEPOS GUIDE TO PAX / EMV / BROADPOS What Is BroadPOS? Some things you can do with BroadPOS What Processors Are Currently Supported? How To Login To BroadPOS Support Checklist Step -1: Things Specific To Processors Tokenization (attach credit card): Batch Out Step 0: Get One Or More VAR Sheets for the Merchant Step 1: Create a New Merchant (if necessary) Step 2: Add the Serial Numbers of the New Terminal(s) Step 3: Create A New Template TSYS Parameters TSYS Tab => Merchant Parameters TSYS Tab => Host Feature First Data Omaha Parameters First Data Omaha Tab => Host Features, Host URLs First Data Rapid Connect Parameters FirstData RapidConnect Tab => Host Features FirstData RapidConnect Tab => Host URLs Heartland Portico Parameters Hsptc Tab => Host Features Hsptc Tab => Merchant Parameters Hsptc Tab => Host URLs Hsptc Tab => Dial Parameters Misc Tab => Communication Tab => General Communication Tab => LAN Communication Tab => Communication between ECR/POS and PAX terminal Communication => POS System Feature (Ethernet Only) Step 4: Deploy The Template Step 5: Install the Browser Extension for Emagine Payments Step 6: Setup Payment Terminals in the Backoffice Step 7: Create New Payment Type for EMV (if necessary) Step 8: Test The Terminal Frequently Asked Questions / Troubleshooting PAX Frequently Asked Questions List CONNECT ERROR when I try to execute a transaction SWIPE ONLY error when I try to Void or Adjust NOTES on First Data Omaha How can I do a manual credit card transaction? Can I Still do a Pre-Authorization? Can I Attach A Credit Card To An Order? TSYS Tokenization Support Heartland Tokenization Support First Data Tokenization Support If I Take A Payment On Station #1 with PAX Terminal #abc, Can I Void / Adjust on Station #2 that has PAX Terminal #xyz How Can I Batch Out? How Can I Check The Batch Status of These Terminals? The Merchant Has An Outbound Firewall - What Rules Do We Need To Whitelist? What about Daylight Savings Time changes? BroadPOS Error: The configuration of source template is not available BroadPOS Error: The source application has not been assigned to the reseller Debugging The Chrome Extension Updating the Extension / Update Settings Useful Contacts / Links PAX Support Heartland Support TSYS Support First Data Omaha Support First Data Rapid Connect Support DataWire Support Our Internal PAX Rollout Database Interlink Credit Card Processing Card Connect What Is BroadPOS? BroadPOS is PAX’s web-based configurator that can be used to manage terminals. One common misconception is that it participates in some way with an actual transaction. This is not true. Once a terminal has been setup and configured, it talks directly to the host processor to execute a transaction. PAX / BroadPOS has no knowledge at all of the actual transactions that are carried out. Some things you can do with BroadPOS ● Deploy/setup a New Terminal ● Update the App on a Terminal ● Update the Parameters on a Terminal ● Reprovision a terminal for a different site / location / app / processor The PAX terminals have both an App and a set of Parameters that configure it. The App is specific to both the model type and the processor type. For example, there’s a specific App for the S300 using Heartland and a different App for the S300 and the TSYS. You need to email PAX @ [email protected] if you need an App but it is not showing up in the ​ ​ dropdown list. They can add it for you, or it may not be available. For example at the time of ​ ​ writing, they do not have an EMV App for the PX5 or PX7 with TSYS or FirstData What Processors Are Currently Supported? At the time of writing they support one of: ● TSYS ● First Data (Omaha) ● First Data Rapid Connect (Nashville) ● Heartland Other processors may be added in the future (e.g. EPX), and note that not all devices have apps for all processors. How To Login To BroadPOS Login to BroadPOS at https://secure.broadpos.com - you should have your own account. If you ​ ​ ​ ​ don’t ask, and one can be created for you. Once you login, you’ll have this sidebar: It is fairly self-explanatory. ● My Merchants is used to manage our merchants. ​ ● My Terminals manages terminals (obviously). ​ ● My Templates are used to roll out similar / same app + parameters to more than one ​ terminal without having to re-type everything. ● User Management allows you to add more users to BroadPOS. ​ Support Checklist Here’s a checklist of what to do when you get a new PAX terminal and it needs to be setup. Step -1: Things Specific To Processors Tokenization (attach credit card): ● Does not work with First Data Omaha ● Works with TSYS ● Works with Heartland ● Supposedly works with First Data Rapid Connect (but unverified) You must explicitly request tokenization to be turned on at the processor to enable it. Query your VAR sheet provider. If they want “attach credit card”, YOU NEED TO ASK THE ​ PROCESSOR TO TURN IT ON. Batch Out Heartland only: if you’re setting up Auto End Of Day with Heartland and configuring an auto ​ batch time on the PAX terminal YOU MUST CONTACT HEARTLAND AND TELL THEM TO ​ BATCH AT THE SAME TIME. If you don’t, transactions will continue to flow in, but never settle. ​ PAX Devices Before you sell a solution with specific PAX devices, make sure PAX has an app for that specific processor. For example, the PX5, PX7 currently only work with Heartland. Do your homework ​ ​ ​ ​ -- ask me first. I can find out the latest, or email [email protected] to ask them directly. ​ ​ Step 0: Get One Or More VAR Sheets for the Merchant Depending on who you’re talking to and what processor is to be used, they may send a VAR sheet per terminal, or they may just send one sheet with a list of different terminal IDs. But you won’t be able to setup the terminals, create the template and deploy until you have these params. See the Useful Contacts / Link section for who to contact if you don’t have a VAR sheet. ​ ​ I do have sheets for testing Heartland’s development servers -- if you just want to set up a terminal to test the hardware. I also have a test batch of cards. Step 1: Create a New Merchant (if necessary) Determine if we need to create a new merchant or not (take a look and see if the merchant already exists). NOTE: the Emagine POS Dev merchant I created to test and do development ​ ​ under. Please don’t delete it. IMPORTANT: For some silly, God-awful reason, PAX has decided to make the merchant name ​ a global value in their system. This means if there’s already a merchant in there named “Joe’s Pizza”, even if was added by someone else and we can’t see it, and you try to add the same name, it will complain that the name is already taken. ¯\_(ツ)_/¯ ​ To work around this silliness, I am adding the Merchant name and then tacking on the word EMAGINE. See, for example how we have Legends EMAGINE as the Merchant name for ​ ​ ​ Legends (Alliance Hospitality is their official business name.) The information above is mainly for our records -- it will not affect processing, but it is best to keep this information current so we can filter by it when we search for templates or terminals. If we have 500 merchants in here, the names should match or be close to the same names as the organization we have in the POS for our sanity. You can ignore the BUSINESS INFORMATION and other drop down sections here. ​ ​ Step 2: Add the Serial Numbers of the New Terminal(s) Serial numbers can be found on the sticker on the back of the device, and also on the outside of the packaging box. You must add them to allow them to be managed. Select My Terminals and choose Add Terminal (SN) in the top right corner: ​ ​ Fill out the form on the next page. The important thing is the serial number. Assign it to the correct merchant that you just created. The Location field is optional and just informational. The Manufacturer Name and Model Name should auto-populate after you enter the serial number. Now the terminal has been added but it isn’t provisioned. The next screen shows this: We can skip this for now and do it later. We’ll have to build a template first. In order to build a template, you need the VAR sheet. Step 3: Create A New Template Templates are useful to save you the hassle of having to re-fill out some fairly painful web forms over and over. This is error prone stuff; it is super easy to make a mistake copying abstract numbers into all these crazy fields, especially if the location is going to deploy more than one physical terminal -- typically all you need to do is change the V Number (more on that later) from the param sheet and update the Terminal ID -- the rest of the parameters stay the same. So, you create the template once, and then when you go to actually deploy it to a specific serial #, you have a chance to make any last minute changes to the parameters and you change a couple fields and push it out. I haven’t yet settled on a good naming standard for templates. If you have a good idea for it let me know. When you create one, they show you the merchant and device as separate fields, so maybe it isn’t necessary to put this information into the template (see below for example).
Load more

Recommended publications
  • NOAA Technical Report NOS NGS 60
    NOAA Technical Report NOS NGS 60 NAD83 (NSR2007) National Readjustment Final Report Dale G. Pursell Mike Potterfield Rockville, MD August 2008 NOAA Technical Report NOS NGS 60 NAD 83(NSRS2007) National Readjustment Final Report Dale G. Pursell Mike Potterfield Silver Spring, MD August 2008 U.S. DEPARTMENT OF COMMERCE National Oceanic and Atmospheric Administration National Ocean Service Contents Overview ........................................................................................................................ 1 Part I. Background .................................................................................................... 5 1. North American Datum of 1983 (1986) .......................................................................... 5 2. High Accuracy Reference Networks (HARNs) .............................................................. 5 3. Continuously Operating Reference Stations (CORS) .................................................... 7 4. Federal Base Networks (FBNs) ...................................................................................... 8 5. National Readjustment .................................................................................................... 9 Part II. Data Inventory, Assessment and Input ....................................... 11 6. Preliminary GPS Project Analysis ................................................................................11 7. Master File .....................................................................................................................11
    [Show full text]
  • A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability
    A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability Mosharaf Chowdhury Rachit Agarwal Vyas Sekar Ion Stoica Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2014-172 http://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-172.html October 11, 2014 Copyright © 2014, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability Mosharaf Chowdhury Rachit Agarwal Vyas Sekar Ion Stoica UC Berkeley UC Berkeley Carnegie Mellon University UC Berkeley ABSTRACT Even though our work does not provide new active mea- We present a retrospective and longitudinal study of Internet surement techniques or new datasets, we believe that there is value in this retrospective analysis on several fronts. First, it latency and path stability using three large-scale traceroute provides a historical and longitudinal perspective of Internet datasets collected over several years: Ark and iPlane from path properties that are surprisingly lacking in the measure- 2008 to 2013 and a proprietary CDN’s traceroute dataset spanning 2012 and 2013. Using these different “lenses”, we ment community today. Second, it can help us revisit and revisit classical properties of Internet paths such as end-to- reappraise classical assumptions about path latency and sta- end latency, stability, and of routing graph structure.
    [Show full text]
  • Misleading Stars: What Cannot Be Measured in the Internet?
    Noname manuscript No. (will be inserted by the editor) Misleading Stars: What Cannot Be Measured in the Internet? Yvonne-Anne Pignolet · Stefan Schmid · Gilles Tredan Abstract Traceroute measurements are one of the main in- set can help to determine global properties such as the con- struments to shed light onto the structure and properties of nectivity. today’s complex networks such as the Internet. This arti- cle studies the feasibility and infeasibility of inferring the network topology given traceroute data from a worst-case 1 Introduction perspective, i.e., without any probabilistic assumptions on, e.g., the nodes’ degree distribution. We attend to a scenario Surprisingly little is known about the structure of many im- where some of the routers are anonymous, and propose two portant complex networks such as the Internet. One reason fundamental axioms that model two basic assumptions on is the inherent difficulty of performing accurate, large-scale the traceroute data: (1) each trace corresponds to a real path and preferably synchronous measurements from a large in the network, and (2) the routing paths are at most a factor number of different vantage points. Another reason are pri- 1/α off the shortest paths, for some parameter α 2 (0; 1]. vacy and information hiding issues: for example, network In contrast to existing literature that focuses on the cardi- providers may seek to hide the details of their infrastructure nality of the set of (often only minimal) inferrable topolo- to avoid tailored attacks. gies, we argue that a large number of possible topologies Knowledge of the network characteristics is crucial for alone is often unproblematic, as long as the networks have many applications as well as for an efficient operation of the a similar structure.
    [Show full text]
  • PAX A920 Mobile Smart Terminal Quick Setup Guide
    PAX A920 QUICK SETUP GUIDE PAX A920 Mobile Smart Terminal Quick Setup Guide 2018000702 v1.8 1 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE PAX A920 Mobile Terminal Intelligence of an ECR in a handheld point of sale. The PAX A920 is an elegantly designed compact secure portable payment terminal powered by an Android operating system. The A920 comes with a large high definition color display. A thermal printer and includes NFC contactless and electronic signature capture. Great battery life for portable use. 2018000702 v1.8 2 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 1 What’s in The Box The PAX A920 includes the following items in the box. 2018000702 v1.8 3 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 2 A920 Charging Instructions Before starting the A920 battery should be fully charged by plugging the USB to micro USB cord to a PC or an AC power supply and then plug the other end with the micro USB connector into the micro USB port on the left side of the terminal. Charge the battery until full. Note: There is a protective cover on the new battery terminals that must be removed before charging the battery. See Remove and Replace Battery section. 2018000702 v1.8 4 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 3 A920 Buttons and Functions Front Description 6 1 2 7 3 8 9 4 5 2018000702 v1.8 5 PAX Technology® Customer Support [email protected] (877) 859-0099 www.pax.us PAX A920 QUICK SETUP GUIDE 3.1 A920 Buttons and Functions Front Description 1.
    [Show full text]
  • PAX-It! TM Applications the Paxcam Digital USB 2.0 Camera System
    Digital Imaging Workflow for Industrial From the Makers of PAX-it! TM Applications The PAXcam Digital USB 2.0 Camera System l Affordable camera for microscopy, with an easy-to-use interface l Beautiful, high-resolution images; true color rendition l Fully integrated package with camera and software l USB 2.0 interface for the fastest live digital color preview on the market l Easy-to-use interface for color balance, exposure & contrast control, including focus indicator tool l Adjustable capture resolution settings (true optical resolution -- no interpolation) l Auto exposure, auto white balance and manual color adjustment are supported l Create and apply templates and transparencies over the live image l Acquire images directly into the PAX-it archive for easy workflow l Easy one-cable connection to computer; can also be used on a laptop l Adjustable region of interest means smaller file sizes when capturing images l PAXcam interface can control multiple cameras from the same computer l Stored presets may be used to save all camera settings for repeat conditions Capture Images Directly to PAX-it Image Database Software Includes PAXcam Video Agent for motion video capture l Time lapse image capture l Combine still images to create movie files l Extract individual frames of video clips as bitmap images Live preview up to 40 fps PAX-it! l File & retrieve images in easy-to-use cabinet/folder structure l Store images, video clips, documents, and other standard digital file types l Images and other files are in a searchable database that you
    [Show full text]
  • Freebsd and Netbsd on Small X86 Based Systems
    FreeBSD and NetBSD on Small x86 Based Systems Dr. Adrian Steinmann <[email protected]> Asia BSD Conference in Tokyo, Japan March 17th, 2011 1 Introduction Who am I? • Ph.D. in Mathematical Physics (long time ago) • Webgroup Consulting AG (now) • IT Consulting Open Source, Security, Perl • FreeBSD since version 1.0 (1993) • NetBSD since version 3.0 (2005) • Traveling, Sculpting, Go AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 2 Focus on Installing and Running FreeBSD and NetBSD on Compact Flash Systems (1) Overview of suitable SW for small x86 based systems with compact flash (CF) (2) Live CD / USB dists to try out and bootstrap onto a CF (3) Overview of HW for small x86 systems (4) Installation strategies: what needs special attention when doing installations to CF (5) Building your own custom Install/Maintenance RAMdisk AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 3 FreeBSD for Small HW Many choices! – Too many? • PicoBSD / TinyBSD • miniBSD & m0n0wall • pfSense • FreeBSD livefs, memstick • NanoBSD • STYX. Others: druidbsd, Beastiebox, Cauldron Project, ... AsiaBSDCon Tutorial March 17, 2011 in Tokyo, Japan “Installing and Running FreeBSD and NetBSD on Small x86 Based Systems” Dr. Adrian Steinmann <[email protected]> 4 PicoBSD & miniBSD • PicoBSD (1998): Initial import into src/release/picobsd/ by Andrzej Bialecki <[email protected]
    [Show full text]
  • Parallel MPI I/O in Cube: Design & Implementation
    Parallel MPI I/O in Cube: Design & Implementation Bine Brank A master thesis presented for the degree of M.Sc. Computer Simulation in Science Supervisors: Prof. Dr. Norbert Eicker Dr. Pavel Saviankou Bergische Universit¨atWuppertal in cooperation with Forschungszentrum J¨ulich September, 2018 Erkl¨arung Ich versichere, dass ich die Arbeit selbstst¨andigverfasst und keine anderen als die angegebenen Quellen und Hilfsmittel benutzt sowie Zitate kenntlich gemacht habe. Mit Abgabe der Abschlussarbeit erkenne ich an, dass die Arbeit durch Dritte eingesehen und unter Wahrung urheberrechtlicher Grunds¨atzezi- tiert werden darf. Ferner stimme ich zu, dass die Arbeit durch das Fachgebiet an Dritte zur Einsichtnahme herausgegeben werden darf. Wuppertal, 27.8.2017 Bine Brank 1 Acknowledgements Foremost, I would like to express my deepest and sincere gratitude to Dr. Pavel Saviankou. Not only did he introduce me to this interesting topic, but his way of guiding and supporting me was beyond anything I could ever hoped for. Always happy to discuss ideas and answer any of my questions, he has truly set an example of excellence as a researcher, mentor and a friend. In addition, I would like to thank Prof. Dr. Norbert Eicker for agreeing to supervise my thesis. I am very thankful for all remarks, corrections and help that he provided. I would also like to thank Ilya Zhukov for helping me with the correct in- stallation/configuration of the CP2K software. 2 Contents 1 Introduction 7 2 HPC ecosystem 8 2.1 Origins of HPC . 8 2.2 Parallel programming . 9 2.3 Automatic performance analysis . 10 2.4 Tools .
    [Show full text]
  • Release 0.11.0
    mpiFileUtils Documentation Release 0.11.0 HPC Sep 29, 2021 Contents 1 Overview 1 2 User Guide 3 2.1 Project Design Principles........................................3 2.1.1 Scale..............................................3 2.1.2 Performance...........................................3 2.1.3 Portability............................................3 2.1.4 Composability..........................................4 2.2 Utilities..................................................4 2.3 Experimental Utilities..........................................4 2.4 libmfu..................................................4 2.4.1 libmfu: the mpiFileUtils common library...........................5 2.4.2 mfu_flist.............................................5 2.4.3 mfu_path............................................5 2.4.4 mfu_param_path........................................5 2.4.5 mfu_io..............................................5 2.4.6 mfu_util.............................................6 2.5 Build...................................................6 2.5.1 Build everything with Spack..................................6 2.5.2 Build everything directly....................................6 2.5.3 Build everything directly with DAOS support.........................8 2.5.4 Build mpiFileUtils directly, build its dependencies with Spack................8 3 Man Pages 9 3.1 dbcast...................................................9 3.1.1 SYNOPSIS...........................................9 3.1.2 DESCRIPTION.........................................9 3.1.3 OPTIONS............................................9
    [Show full text]
  • Z/VM Version 7 Release 2
    z/VM Version 7 Release 2 OpenExtensions User's Guide IBM SC24-6299-01 Note: Before you use this information and the product it supports, read the information in “Notices” on page 201. This edition applies to Version 7.2 of IBM z/VM (product number 5741-A09) and to all subsequent releases and modifications until otherwise indicated in new editions. Last updated: 2020-09-08 © Copyright International Business Machines Corporation 1993, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures................................................................................................................. xi Tables................................................................................................................ xiii About this Document........................................................................................... xv Intended Audience..................................................................................................................................... xv Conventions Used in This Document......................................................................................................... xv Escape Character Notation................................................................................................................... xv Case-Sensitivity.....................................................................................................................................xv Typography............................................................................................................................................xv
    [Show full text]
  • An Airborne Network Telemetry Link for the Inet Technical Demonstration System
    An Airborne Network Telemetry Link for the iNET Technical Demonstration System Item Type text; Proceedings Authors Temple, Kip; Laird, Daniel Publisher International Foundation for Telemetering Journal International Telemetering Conference Proceedings Rights Copyright © held by the author; distribution rights International Foundation for Telemetering Download date 25/09/2021 05:15:29 Link to Item http://hdl.handle.net/10150/606170 AN AIRBORNE NETWORK TELEMETRY LINK FOR THE INET TECHNICAL DEMONSTRATION SYSTEM Kip Temple Air Force Flight Test Center, Edwards AFB CA Daniel Laird Air Force Flight Test Center, Edwards AFB CA ABSTRACT A previous paper was presented [1] detailing the design and testing of the first networked demonstration system (ITC 2006) for iNET. This paper extends that work by testing a commercial off the shelf (COTS) solution for the wireless network connection of the Telemetry Network System (TmNS). This paper will briefly discuss specific pieces of the airborne and ground station system but will concentrate on the new wireless network link, how it was tested, and how well it performed. Flight testing results will be presented accessing the performance of the wireless network link. KEY WORDS integrated Networked Enhanced Telemetry (iNET), wireless network link, Telemetry Network System (TmNS), serial streaming telemetry INTRODUCTION The iNET Team has assembled a Demonstration System to not only assess COTS wireless network link performance within the aeronautical test environment but also to demonstrate the potential uses of a network linked system. The TmNS is shown pictorially in Figure 1. The four components are the vehicular network, or the Test Article Segment (TAS), the interface to the ground station, or Ground Station Segment (GSS), the wireless network link that ties the two networks together, and the legacy serial streaming telemetry (SST) link.
    [Show full text]
  • LDM7 Deployment Guidance
    LDM­7 Deployment Guidance Steve Emmerson, University Corporation for Atmospheric Research ([email protected]) ​ ​ Malathi Veeraraghavan, University of Virginia ([email protected]) ​ ​ Multicast network test To install LDM­7, you will need a Linux/Unix machine and a copy of the LDM­7 software package. Also, you need to make sure the network that LDM­7 is going to run on supports and has enabled multicast. To test whether multicast is supported, please follow the link https://github.com/shawnsschen/CC­NIE­Toolbox/tree/master/generic/mcast_test and obtain the two C files. One is for multicast sender and the other for receiver. If there are more than one network interfaces in the sender’s system, you have to manually update the routing table with one new entry: route add 224.0.0.1 dev eth1. Then use route ­n to check the updated routing ​ ​ ​ table. You will be able to see something like: Note that the entry we added is only matching a particular multicast address 224.0.0.1, not a subnet. If the multicast address changes, you need to manually change the configuration or use a subnet address. Now you have a multicast network (though not sure if it works), next step is to upload the mcast_send.c onto the sender system and mcast_recv.c onto all the receiver systems (more than one in a multicast network). Use the following command to compile them, respectively: gcc ­o send mcast_send.c gcc ­o recv mcast_recv.c send is a multicast sender­side test program, it sends out a “hello multicast world” message every second to multicast group 224.0.0.1:5173.
    [Show full text]
  • Objections to Killer Robots
    DEADLY Decisions objections to 8 killer robots Address: Postal Address: Godebaldkwartier 74 PO Box 19318 3511 DZ Utrecht 3501 DH Utrecht The Netherlands The Netherlands www.paxforpeace.nl [email protected] © PAX 2014 Authors: Merel Ekelhof Miriam Struyk Lay-out: Jasper van der Kist This is a publication of PAX. PAX is a founder of the Campaign to Stop Killer Robots. For more information, visit our website: www.paxforpeace.nl or www.stopkillerrobots.org About PAX, formerly known as IKV Pax Christi PAX stands for peace. Together with people in conflict areas and critical citizens in the Netherlands, we work on a dignified, democratic and peaceful society, everywhere in the world. Peace requires courage. The courage to believe that peace is possible, to row against the tide, to speak out and to carry on no matter what. Everyone in the world can contribute to peace, but that takes courage. The courage to praise peace, to shout it from the rooftops and to write it on the walls. The courage to call politicians to accountability and to look beyond your own boundaries. The courage to address people and to invite them to take part, regardless of their background. PAX brings people together who have the courage to stand for peace. We work together with people in conflict areas, visit politicians and combine efforts with committed citizens. www.PAXforpeace.nl The authors would like to thank Roos Boer, Bonnie Docherty, Alexandra Hiniker, Daan Kayser, Noel Sharkey and Wim Zwijnenburg for their comments and advice. First, you had human beings without machines. Then you had human beings with machines.
    [Show full text]