--- title: Obtain PSP Credentials slug: payments/obtain-psp-credentials description: Obtain and enter your Payment Service Provider credentials in Unaric Payments to start accepting live transactions. image: https://archbee-image-uploads.s3.amazonaws.com/10Nod6Ww95R3dPr0k0TCJ/G1PLebwJ4Stuf2TYZy-9z_unaric-payments.png docTags: createdAt: 2025-02-06T17:53:40.348Z --- Unaric Payments will require credentials to connect to a user's payment service provider. Required credentials are not consistent across providers. This page provides instructions on how to obtain the credentials for connecting PSPs. For PSPs not listed, you will need to contact your provider for instructions. ::::ExpandableHeading ## Adyen  | **Credential** | **How to obtain** | | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Merchant Account** | The name of your Adyen company/merchant account. | | **API Key** | Follow the instructions to generate your API key in [API credentials \| Adyen Docs](https://docs.adyen.com/development-resources/api-credentials/#generate-your-api-key/). | | **Client Key** | See [Get your client key \| Adyen Docs](https://docs.adyen.com/development-resources/client-side-authentication/#get-your-client-key). | | **URL Prefix** | The URL prefix is a combination of `[Random]-[Companyname]`. For staging environments, you can use any value; for live servers, navigate to **Live Customer Area > Account > API URLs** to retrieve the URL prefix. More information on URL prefixes in [Live endpoints \| Adyen Docs](https://docs.adyen.com/development-resources/live-endpoints/#live-url-prefix). | :::hint{type="info"} To use Adyen for sandbox and test transactions, see [Sandbox Installation & Testing](docId\:qMPpUk9rKjuswRJL_uCjb). ::: :::: ::::ExpandableHeading ## Authorize.net | **Credential** | **How to obtain** | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | **API Login ID** | The **API Login ID **can be found in **Account > Settings > API Credentials & Keys** in your Authorize.net account. | | **Transaction Key** | Navigate to **Account > Settings > API Credentials & Keys** in your Authorize.net account and create a **Transaction Key**. | :::hint{type="warning"} Creating a new **Transaction Key **will expire the old one in 24 hours,and may affect existing API integrations. ::: :::: :::ExpandableHeading ## Braintree You will need to log in to the Braintree Dashboard using the corresponding URL: - For test/sandbox: [https://sandbox.braintreegateway.com/login](https://sandbox.braintreegateway.com/login) - For live/production: [https://www.braintreegateway.com/login](https://www.braintreegateway.com/login) | **Credential** | **How to obtain** | | --------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Merchant ID** | Navigate to the Braintree Dashboard. Under **Account > My User**, go to the **API Keys, Tokenization Keys, Encryption Keys** section and click **View Authorizations**. Your Merchant ID will be displayed here. | | **Private Key** | In the **API Keys, Tokenization Keys, Encryption Keys** section, click **Generate New API Key**. Once generated, click **View** under the **Private Key** heading to reveal the Private Key. | | **Public Key** | The Public Key will be displayed alongside the newly generated API Key. | ::: ::::ExpandableHeading ## Checkout.com  | **Credential** | **How to Obtain** | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Secret Key** | 1. Log in to the unified Checkout.com Dashboard:
- **For both Live and Test/Sandbox environments:** [https://dashboard.checkout.com/](https://dashboard.checkout.com/). To switch between your live and sandbox data, use the environment toggle found in your profile selector or navigation bar.
2. On the top navigation bar of the dashboard, select the **Developers** icon.
3. Open the **Keys** tab from the submenu.
4. Your Secret and Public API keys will be displayed on this page. | :::hint{type="info"} For security reasons, you can only view your secret API key in full when you first create it.If the existing key is partially masked and you didn't save it, you will need to click **Create a new key** to generate a new visible one. ::: :::hint{type="info"} For test accounts, you can sign up directly on their website. However, you must contact Checkout.com support ([support@checkout.com](mailto\:support@checkout.com)) to enable the "Full Card Details API." ::: :::: :::ExpandableHeading ## CyberSource | **Credential** | **How to obtain** | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **CyberSource Merchant ID** | 1. Log in to the CyberSource dashboard.
2. Ensure you select the appropriate **Live** or **Test** business center.
3. Your Merchant ID is the same as the **Organization ID** used to access the CyberSource dashboard. | | **Security Key** | 1. In the CyberSource dashboard, select **Account Management** from the left-hand menu, then choose **Transaction Security Keys**.
2. Click the **Security Keys for the SOAP Toolkit API** link.
3. Click the **Generate Key** button. A box will appear containing the new key. Copy the key immediately, as it will only be displayed once. | | **Org ID** | The **Org ID** is the same as the **Organization ID** used to log in to the CyberSource dashboard. | ### IP Whitelisting If your CyberSource account has IP range restrictions enabled, you will need to add the Unaric Payments server addresses to the IP whitelist. Follow these steps: 1. In the CyberSource dashboard, go to **Account Management** and select **Configure IP Settings**. 2. If the box marked **Enable IP verification** is checked, IP restrictions are in place. 3. Add the following IP addresses to the whitelist: - For live running: 162.13.56.213 - For testing: 77.68.42.36 ::: :::ExpandableHeading ## GoCardless Unaric Payments will redirect you to the GoCardless sign-up page to complete your details and obtain a GoCardless account. If you already have a GoCardless account, click the** Sign in** link at the bottom of the form and enter your details as required. Once complete you will see a message from Unaric Payments confirming the connection. ::Image[]{src="https://api.archbee.com/api/optimize/10Nod6Ww95R3dPr0k0TCJ/RSKIEOju95wP-2VhsjBxM_output.gif" size="72" width="2018" height="1080" darkWidth="2018" darkHeight="1080" position="center" showCaption="false"} ::: :::ExpandableHeading ## IntelliPay | **Credential** | **How to Obtain** | | ---------------- | -------------------------------------------------------------------------------------------------- | | **Merchant Key** | Contact Intellipay's customer support at [support@intellipay.com](mailto\:support@intellipay.com). | | **API Key** | Contact Intellipay's customer support at [support@intellipay.com](mailto\:support@intellipay.com). | ::: :::ExpandableHeading ## Moneris - **For Testing**: Use the credentials obtained from the Moneris developer portal: [https://api-developer.moneris.com/](https://developer.moneris.com/). - **For Live**: Use the credentials obtained from your live merchant account: [https://login.moneris.com/en/login](https://login.moneris.com/en/login). | **Credential** | **How to obtain** | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Username** | This is the same username you use to log in to the Moneris developer portal or live merchant account. | | **Store ID** | **For Testing**:
1. In Moneris, under **My Profile,** scroll down to the **Credentials** section. Your Store ID will be displayed here.
**For Live**:
Navigate to **Admin > Store Settings**. The Store ID will be displayed. | | **API Key** | **For Testing**:
2. Under **My Profile** on the right-hand side, scroll down to the **Credentials** section. Your API Key will be displayed here.
**For Live**: Navigate to **Admin > Store Settings**. The API Key will be displayed at the top of the page. | ::: :::ExpandableHeading ## Payline | **Credential** | **How to obtain** | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Contract Number** | This is the **VAD (Vente à Distance)** contract number. It should have been provided by Payline when you opened your account. If you don’t have it, check your contract or contact Payline support. For testing, you might use a fake number like 7654321. | | **Merchant ID** | Also called **Merchant's Login** or **Identifiant Commerçant**, this is a long numeric field. It should have been provided by Payline when you opened your account. If you don’t have it, check your contract or contact Payline support. | | **Access Key** | A long alphanumeric key. It should have been provided by Payline when you opened your account. If you don’t have it, you can find or generate a new one:
1. Log in to the Payline admin website.
- For **testing**: [https://homologation-admin.payline.com](https://homologation-admin.payline.com)
- For **live**: [https://admin.payline.com](https://admin.payline.com/)
2. Under the **Settings** tab, click on **Change your access key** (or **Configuration > Gestion des clés d'accès**).
3. View or generate a new **Access Key**. | ::: :::ExpandableHeading ## PayPal | **Credential** | **How to obtain** | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Client ID & Secret Key** | 1. Go to [https://developer.paypal.com](https://developer.paypal.com/) and use your PayPal business credentials to log in.
2. In the options shown on the top right select **Dashboard**.
3. In the** My Apps & Credentials** menu option, find the** REST API apps **section. If no app already exists, click the** Create App** button and give your new app a name.
4. Click the app's name to open it. In the REST API apps section you will find the **Client ID** and **Secret Key**. Make sure you select either Sandbox or Live in the box on the top right of the screen to get either the test or live keys as appropriate. | ### Additional configuration PayPal will not let you run any of their screens in an iframe or overlay, and outside of this the whole process is managed by re-direction. As such, you will need to use the Unaric Payments PostMessage event **asp--redir\:REDIR URL** to determine where the redirection should go when using iframe techniques. Moreover, because the PayPal payment is managed by re-direction you need to set the Cancel, Success and Fail endpoints on the payment record before you launch the Unaric Payments paypage so that you can control what happens when the payment transaction completes. For more information on these fields, see [Post-Payment Redirection URLs](docId\:X1eppA5AidlXMbvROrmlb). ::: :::ExpandableHeading ## Opayo (formerly ***Sage Pay***) | **Credential** | **How to obtain** | | --------------- | ----------------------------------------------------------------------------------------------------------------------------- | | **Vendor Name** | This is the same as your Opayo account credentials. If you do not know your Vendor Name, contact your Sage Pay Administrator. | ### IP Whitelisting Opayo performs IP validation checks, so you will need to whitelist Unaric Payments’ IP addresses in your Sage Pay account so Unaric Payments can communicate with Opayo's gateway. 1. Log into [https://live.sagepay.com/mysagepay/](https://live.sagepay.com/mysagepay/) 2. Under the **Settings** tab, select **Valid IPs**. 3. Click the **Add** button and enter the following details: - **For Testing**: - IP Address: 35.179.25.58 - Subnet Mask: 255.255.255.255 - Description: Unaric Payments test - **For Live Running**: - IP Address: 35.177.118.40 - Subnet Mask: 255.255.255.255 - Description: Unaric Payments live ::: ::::ExpandableHeading ## Stripe  ### 1. Connect Stripe 1. In the **Unaric Payments Setup **tab, click **New PSP connection**. 2. Select **Stripe Connect** as your PSP connection. You will be redirected to Stripe’s sign-up page: - **New users:** Complete the sign-up form. - **Existing users:** Click **Sign in** and enter your credentials. 3. Once complete, Unaric Payments will confirm the connection. ### 2. Update Stripe configuration Stripe uses a set of security rules to discourage merchants who might not have implemented appropriate security measures from processing raw card data. You must disable this security check to prevent it from blocking Unaric Payments transactions processed on your behalf. To disable this feature and allow the handling of raw card data you need to obtain one of the documents listed on Stripe website and submit a support case. For more information, see [Enabling access to raw card data APIs](https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis). Before you submit a support case with Stripe, request the latest Attestation of Compliance (AoC) document from Unaric Payment support at [support@unaric.com](mailto\:support@unaric.com). :::hint{type="success"} Unaric Payments is Level 1 PCI-DSS compliant. As such disabling this feature and allowing the handling of raw card data does not lessen the security of your transactions processed via Unaric Payments. ::: :::: ::::ExpandableHeading ## Vanco | **Credential** | **How to obtain** | | ------------------ | ----------------------------------------------------------- | | **Username** | Provided in setup emails from your integrations specialist. | | **Password** | Provided in setup emails from your integrations specialist. | | **Client ID** | Provided in setup emails from your integrations specialist. | | **Encryption Key** | Provided in setup emails from your integrations specialist. | :::hint{type="info"} If you do not have an integrations specialist or cannot find the original emails, **contact Vanco** to request these credentials. ::: :::: ::::ExpandableHeading ## Vantiv (Worldpay) | **Credential** | **How to obtain** | | ----------------- | ----------------------------------------------------------- | | **Merchant Code** | Supplied by Vantiv for both pre-live and live environments. | | **Username** | Supplied by Vantiv for both pre-live and live environments. | | **Password** | Supplied by Vantiv for both pre-live and live environments. | :::hint{type="warning"} These credentials are different from those used to log in to the Vantiv Merchant Management Service. ::: :::: :::ExpandableHeading ## Worldpay WPG | **Credential** | **How to obtain** | | ----------------- | ------------------------------------------------------------- | | **API Id (iss)** | Supplied by Worldpay for both pre-live and live environments. | | **Merchant Code** | Supplied by Worldpay for both pre-live and live environments. | | **Password** | Supplied by Worldpay for both pre-live and live environments. | | **Org Unit ID** | Supplied by Worldpay for both pre-live and live environments. | | **API Key** | Supplied by Worldpay for both pre-live and live environments. | :::