Authentication Guide

---

Introduction

In order to have access to our web services, each integrator receives a set of unique store credentials. The store credentials consist of a) Store ID and b) Store key. You will receive a set of demo store credentials at the beginning of your integration that are for your demo merchant. If you did not receive these please reach out to your Implementation Coordinator. These demo store credentials will only be valid for your demo merchant. At the completion of the API certification process, you will be provided your production store credentials. In addition to the store credentials, an integrator must also have the EntityID and LocationID of the Merchant and Location for the transaction or reporting API calls. The EntityID, also referred to as the Merchant ID or MID, is a unique value assigned to each merchant. The LocationID or LID is a unique value assigned to the location of each merchant referencing the settlement account.

See the table below for definitions.

NAME	DESCRIPTION
EntityId	The entityId is a unique identifier that is systematically generated when the merchant is installed on the EPS system. It is also referred to as the Merchant ID or MID.
StoreId	A unique user ID systematically generated by EPS upon installing a web service user. The storeId can be unique to each individual merchant, or a master storeId can be assigned at the reseller/owner level.
StoreKey	A unique password systematically generated by EPS upon installing a web service user. The password corresponds with the storeId above.
LocationId	The locationId is a unique identifier for each location (account) set up under a user. Users that process transactions for multiple accounts, or use the same account for multiple purposes (i.e. building fund, donations, dues), will be assigned individual location IDs for each.

Getting Started

Perform the following examples to test your credentials to confirm your connectivity.

• Payment Vault - https://ws.eps.profitstars.com/PV/PaymentVault.asmx Test Connection First, we want to verify that you can connect successfully to the endpoint. Run this example TestConnection to verify.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pv="https://ssl.selectpayment.com/PV">
    <soapenv:Header/>
    <soapenv:Body>
        <pv:TestConnection/>
    </soapenv:Body>
</soapenv:Envelope>

You should receive this successful response

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
    <TestConnectionResponse xmlns="https://ssl.selectpayment.com/PV">
        <TestConnectionResult>true</TestConnectionResult>
    </TestConnectionResponse>
</soap:Body>
</soap:Envelope>

Test Credentials

Next, we want to try the demo credentials provided to you to make sure you can successfully authenticate. Run this example TestCredentials with your demo credentials.

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pv="https://ssl.selectpayment.com/PV">
<soapenv:Header />
<soapenv:Body>
    <pv:TestCredentials>
        <pv:storeId>your storeid</pv:storeId>
        <pv:storeKey>your storekey</pv:storeKey>
        <pv:entityId>your entityid</pv:entityId>
        <pv:locationId>your locationid</pv:locationId>
        <pv:terminalNumber>__WebService</pv:terminalNumber>
    </pv:TestCredentials>
</soapenv:Body>
</soapenv:Envelope>

You should receive this successful response

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
    <TestCredentialsResponse xmlns="https://ssl.selectpayment.com/PV">
        <TestCredentialsResult>
            <returnValue>Success</returnValue>
            <message>Operation successful</message>
        </TestCredentialsResult>
    </TestCredentialsResponse>
</soap:Body>
</soap:Envelope>

Next Steps

If all is successful you are ready to move on and get working with some of our other guides. If not, we are here to help you get up and running, so reach out to us and we will work with you to find a solution.

• Explore our payment guides We have custom-built guides to show how to leverage our APIs in common use case scenarios. Take a look to find the one that fits your business needs.
• Review the API Reference Our guides are a great starting point, but the API Reference will provide full details for all our available APIs and their technical specifications.