Contract configuration

To start processing transactions with a provider, you first need to configure your contract with them. It's a good idea to configure the contract on sandbox first to see if transactions are passing correctly. You can also perform negative testing to check if you can handle errors and failures. 

The next step is to configure the contract on your live environment. The configuration is very similar to sandbox, with a few updates to, for example, gateway URL. 

Sometimes you need to configure only your Merchant portal but in many cases, you need to set up the provider's end as well.

Adyen (JSON)

Adyen (JSON) - sandbox

Adyen portal

Make sure that you copy the following data that you generate in Adyen's portal as you'll need those for your Merchant portal: Web Service User Name, Password, HMAC Key, Account Code, and skinCodeskinHmacKey.

1. Log in to the Adyen portal: https://ca-test.adyen.com/.
2. In your top navigation, go to Account > Merchant accounts. Copy the Account Code for your account. You'll have to enter it in your Merchant portal. 
3. Go to Account > API credentials. Click on the Name link for the Web Service. 
4. Go to the Basic Auth tab and click Generate Password. This password will be used by the system to send notifications to the web service. 
5. Go to Account > Server communication and click Add for Standard Notification.
6. For sabdbox, enter the URL: https://api.sandbox.oscato.com/notification/ADYEN-JSON/MERCHANT_CODE/do.html replacing the <MERCHANT_CODE> with your own orchestration platform merchant code. 
7. Select JSON as the Method.
8. Expand Additional Settings and click Generate new HMAC key.
9. Click Save Configuration.

10. Go to Account > Skins and click Create a new skin. 

11. Click to generate a new HMAC key for the skin. Record the key value and the Skin Code value for later. 

12. Click to generate a new HMAC key for the live platform. Copy the key value and the skin code. You will need them when you'll be configuring the live environment.

13. Click Save new HMAC key(s).

14. Click Create New Skin on Test.

15. Go to Account > Settings. In the Capture Delay, select Manual. In this way, you'll only be authorising the payment. To settle the payment, you'll need to make a capture using the API or the interface. With manual capture, you can cancel an authorization on an uncaptured payment, if necessary.

Now, configure the Merchant portal. 

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Expand the dropdwon on the provider's icon and select Adyen-JSON.
   
6. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Adyen. 
7. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
8. Click Continue. 
9. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •  Gateway URL (sandbox): https://pal-test.adyen.com/pal/servlet
   •  hmacKey: enter the key copied from the Adyen portal.
   •  hppPayURl:this is the hosted payment page URL needed for redirect payments; enter https://test.adyen.com/hpp/skipDetails.shtml
   •  is3DSecSupported: select if you support 3D Secure transactions
   •  merchantAccount: enter the name copied from the Adyen portal
   •  skinCode: enter the Skin Code you copied from the Adyen portal
   • skinHmacKey: enter the Skin HMAC key you copied from Adyen portal 
   • checkoutApiUrl: enter https://checkout-test.adyen.com/checkout/v40/payments; this field is optional
   • googleMerchantIdentifier: Google Pay identifier provided by Adyen if you use Google Pay
   • is3DSecureV2Supported: select if you support the 3D Secure 2 transaction flow
   • isAutoCapture: leave empty if you've selected Manual in the Delay capture in the Adyen portal. If you select the option, PREAUTHORIZATION gets disabled. Selecting the parameter enables automatic capture by Adyen. This is done immediately after authorization and removes the need for a capture operation. If you select the option, make sure to change the setting in the the Adyen portal as well. 
   • isTestEnv: select this option for sandbox
   • loadingContext: enter  https://checkoutshopper-test.adyen.com/checkoutshopper/. This is an Adyen's SDK parameter to determine the test versus the produstion environment. This field is optional.
   • Login: enter the Account Code copied from Adyen
   • originKey: enter the value provided by Adyen if you use Google Pay
   • Password: enter the password generated for the Web Service in Adyen.
   • Security Token: leave empty

11. Add any costs and transaction limits that apply as per the contract.

12. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

13. Click Finish.

Adyen (JSON) - live

Follow the configuration steps presented in the sandbox section. 

Make sure you change the following for live:

In the Adyen portal:

• Log in to and configure the live Adyen portal:  https://ca-live.adyen.com
• In the Notification URL section of the Adyen portal, enter the following URL: https://api.live.oscato.com/notification/ADYEN/<MERCHANT>/do.html replacing the. <MERCHANT> with your Merchant portal code.
• Redirect skin. You can only configure the redirect skin in the adyentest console and then published to live. Do the following

1. Log in to https://ca-live.adyen.com. 

2. Go to Account > Skins and click on the link for your testing environment. 

3. When you created the test environment, you generated the key for the live platform as well. Now, click the Publish tab, and click Publish to Live. 

In the Merchant portal, you need to change the parameters in the API parameters section

• Enter the parameters you generated in the Adyen live environment. You'll need a live environment HMAC key, notification URL, password,  and skin code that you can generate in the live Adyen portal.
• Make sure you undelect the isTestMode
• Enter the Gateway URL you receive from Adyen (in this format: https://[random value]-[company name]-pal-live.adyenpayments.com/pal/servlet).
• Enter the following hppPayURL: https://live.adyen.com/hpp/skipDetails.shtml
• If needed, enter the loadingContext for live: https://checkoutshopper-live.adyen.com/checkoutshopper/
• If needed, enter the checkoutApiURL: https://checkout-live.adyen.com/checkout/v40/payments

AfterPay

AfterPay - sandbox

Configure the Merchant portal

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   • AuthKey: Provided  by  AfterPay account  manager;  can be different for each country for which you accept payments. This value is for Germany only. 
   • Gateway URL: https://sandboxapi.horizonafs.com/eCommerceServicesWebApi/
   • Provider Country: 2-character country code. This value is used to display AfterPay's country-specific privacy statement and terms and conditions.The possible values for this field are: Germany (de), Austria (at), Switzerland (ch), Belgium (be), Norway (no), Finland (fi), Sweden (se), Denmark (dk) and Netherlands (nl).
   • Login: enter your username from the Braintree portal
   • Merchant ID: enter the details provided by AfterPAY account manager. Leave as empty if not provided.
   • Password: enter the password from the Braintree portal
   • Security Token: leave empty
   •  Shop logo Url: enter the URL to your shop's logo that will be displayed  at  the  top  of  the  order  page  in MyAfterPay.

8. Click Continue.

9. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with AfterPay. 

10. Add any costs and transaction limits that apply as per the contract.

11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

12. Click Finish.

• If you use a  PRESET and want the transaction to go through without verification, ensure the value of accountValidationType in the checkout configuration is set to NONE. 
• The AFTERPAY_CAMPAIGN and AFTERPAY_INSTALLMENTS networks require additional ACTIVATION call before the CHARGE request to get the available installment plans or available campaigns from AfterPay. The installment plans are returned in the parameter activated.formData.installments. In the native integration scenario, the chosen installment plan must be passed into the CHARGE request as the installment.planId parameter. In case of hosted integration, ACTIVATION is called, when a customer clicks the 'Check rates availability'/'Check available installment plans'/ 'Check available campaigns' button.
• AfterPay validates customer billing and shipping addresses. If address validation fails, the CHARGE request will return the Rejected result code and the correct address in the customerCollectedDetails. 
• Some payment methods (especially installments) might not be available for some customewrs due to risk checks. The availability can only be checked only during the CHARGE request. If the selected payment method is not available, CHARGE request will return the result code 50005.AFTERPAY.400.108 and the message: "Invalid payment method selected". Yoou can't check if a payment method is available during the ACTIVATION phase.
• To use the AFTERPAY_CAMPAIGN (Campaign Invoice) or AFTERPAY_SINGLEINVOICE (Consolidated Invoice) payment methods a setup change needs to be made by AfterPay.
• If the AFTERPAY_SINGLEINVOICE (Consolidated Invoice) method is used no other AfterPay payment methods will be available.
• AFTERPAY_DIRECTDEBIT is available only in the following countries: Germany, Austria and Netherlands.
• Transaction ID can be a maximum of 18 characters and must be unique. Anything more than 18 characters will be truncated. The value is always truncated from the beginning.For example: 12345678901234567890 would change into 345678901234567890.
• If a transaction is being run for Netherlands, then the address provided must be a valid address in the Netherlands. Any other country's address and the transaction might fail a risk check on AfterPay's side.
• Make sure you provide the mandatory parameters to send a complete request:
   - Salutation (for Netherlands and Belgium)
   - SSN (for Sweden, Norway, Finland, Denmark)
   - First name (for all the supported countries)
   - Last name (for all the supported countries)
   - Email (for all the supported countries)
   - Country (for all the supported countries)
   - Postal code (for all the supported countries)
   - Street (for all the supported countries)
   - City (for all the supported countries)
   - Street number (for Germany, Austria, Switzerland, Netherlands, Belgium, Denmark)
   - Mobile phone (for Netherlands and Belgium). 
   The Netherlands: Phone number in the Netherlands is 10 digits long. For example: Landline: 0207230280, Mobile:  0612345678. If you use an area code it can be longer. For example: 0031612345678, +31612345678.  So instead of 00310612345678  send 0031612345678 (remove the zero in between). 
   Belgium: Landline is 9 digits: 012345678, Mobile is 10 digits: 0461234567. If you use an area code it can be longer. For example: 0031612345678, +31612345678
   - Date of birth (for Netherlands and Belgium)
   - Products (shopping cart) information (for all the supported countries)
   - Product code and product amount (for all the supported countries)
   - Billing address

AfterPay - live

Follow the configuration for sandbox. 

Make sure you update the Gateway URL in the API Parameters section of the Contract configuration to: https://api.afterpay.io/

Be2Bill (Dalenys)

Be2Bill - sandbox

To set up your sandbox, you need to configure the Be2Bill portal and your Merchant portal. 

Configure Be2Bill portal for the transactions to go through:

1. Log in to https://extranet-test.be2bill.com/ with the credentials you received from the provider. 
2. Go to Accounts > Account list and click the configuration icon for the account you want to update. 
3. In the Notifiation Settings, enter the Transaction notification URL. The URL is the following: https://{DOMAIN}/notification/BE2BILL/{MERCHANT_CODE}/do.html. The domain for your sandbox is api.sandbox.oscato.com and the <MERCHANT_CODE> is the merchant code from your orchestration platform. 
4. Scroll down to the Redirection URL and enter the data fot the two URL required. In both cases the domain for your sandbox is api.sandbox.oscato.com and the <MERCHANT_CODE> is the merchant code from your orchestration platform.
   • Redirection URL after payment form or 3DSECURE processing: https://{DOMAIN}/decision/BE2BILL/{MERCHANT_CODE}/do.html?type=accept
   • Redirection URL after payment form cancelling: https://{DOMAIN}/decision/BE2BILL/{MERCHANT_CODE}/do.html?type=decline
5. Click Validate. 

Configure your Merchant portal

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •   Gateway URL: enter https://secure-test.be2bill.com/front/service/rest/process 
   •   Identifier for Carte Bancaire: if you use this payment method, enter the identifier. You can find it in the Be2Bill portal in Accounts > Account list in the Identifier column for the Account.
   • Identifier for CreditCard networks: if you use Visa or Mastercard, enter the identifier. You can find it in the Be2Bill portal in Accounts > Account list in the Identifier column for the Account (for example: PAYONEER_CC). 
   • Password for Carte Bancaire network?: if you use this method, enter the password received from Be2Bill. 
   • Password for CreditCard network?: if you use this method, enter the password received from Be2Bill. 
   •  Enable 3D Secure: select to enable 3D secure for your transactions
   •  Login: enter your username from the Be2Bill portal
   •  Password: enter the password from the Be2Bill portal
   •  Security Token: leave empty
   •  Skip 3D Secure for Registration: when selected, users will not be prompted for additional identification when creatingan account.

8. Click Continue.

9. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Be2Bill. Note that Be2Bill only supports Euro (EUR) for Germany (DE).

10. Add any costs and transaction limits that apply as per the contract.

11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

12. Click Finish.

Be2Bill - live

You need to update the configuration in your Be2Bill portal. Follow the sandbox configuration for the Be2Bill portal and update all the URLs that contain <DOMAIN> to have the live domain instead of test. The live domain is: api.live.oscato.com. 

In the Merchant portal, make sure you update the Gateway URL with the URL you obtain from Be2Bill.

Braintree

Braintree - sandbox

Configure Braintree

1. Log in to Braintree: https://sandbox.braintreegateway.com/login
2. Click the cog wheel icon in the top right-hand corner and click API.
3. Click Generate New API Key in the Public Key section. Copy the key for the Merchant portal. 
4. Click View next to the key and copy the Private key  and the Merchant ID values for later. 
5. Click Generate New Tokenization Key. Copy the key for the Merchant portal. 
6. To configure notifications, click the Webhooks tab > Create New Webhook. 
7. Create a webhook destination URL on your server and copy this address to the URL field on the New Webhook page. 
8. Select the notifications you want to receive and click Create Webhook.
9. If you want to use Google Pay or Apple Pay, go to cog wheel > Processing and toggle on Google Pay and Apple Pay. For Apple Pay, you also need to add all domains and subdomains used by your payment page (and the summary page in the case of a PRESET flow) otherwise there might be issues confirming a payment with Apple Pay. To do that, click Options in the Apple Pay section.

Configure Merchant portal

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •   braintreeJsAuthorisation: enter the value of the Tokenization Key you generated in Braintree.
   •  braintreeMerchantId: enter the ID from Braintree
   •  braintreePrivateKey: enter the key generated in Braintree
   •  braintreePublicKey: enter the key generated in Braintree
   •  Gateway URL: http://localhost
   •  googleMerchantId: enter the ID from Google. Follow Google's documentation to register your domain and receive a merchant ID. See https://developers.google.com/pay/api/web/guides/test-and-deploy/integration-checklist
   •  appleMerchantId?: enter the ID from Apple. Contact Apple Pay support to  receive a merchant ID. 
   •  isTest: select for sandbox
   •  Login: enter your username from the Braintree portal
   •  Password: enter the password from the Braintree portal
   •  Security Token: leave empty
   • testSettle: when selected, we will automatically settle payments submitted for settlement in the test environment. Allows for immediate refund testing.

8. Click Continue.

9. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Braintree. 

10. Add any costs and transaction limits that apply as per the contract.

11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

12. Click Finish.

Braintree - live

You will need to configure the Braintree live portal to get the new merchant ID and API keys. The login information will also be different than for sandbox. 

Follow the sandbox guide and repeat the actions in the Braintree live portal: https://www.braintreegateway.com/login. 

When you have the data, configure your live Merchant portal and enter the new data in the API Parameters section. Make sure you don't select the isTest and testSettle options. 

Your live Gateway URL is:  https://secure-magenta1.dalenys.com/front/service/rest/process

ComGate

ComGate - sandbox

To set up your sandbox, you need to configure the ComGate portal and the Merchant portal.

Configure ComGate

1. Login to https://portal.comgate.cz/en/login with the credentials provided by ComGate
2. Click Integration > E-shops settings. 
3. Click the shop for which you would like to make the changese.
4. Click the Shop connections tab and click the pencil icon to edit the shop.
5. Copy the Shop connection identifier and the Password for the Merchant portal.
6. To allowlist redirects and notification URLs, you need to add them in the URL fields: 

ComGate - live

Contact ComGate support to switch to the live version of the ComGate portal. In the live version, you need to update the redirect and notification URLs to contain the live domain: api.live.oscato.com. See the sandbox guide for the menupath. 

Your Merchant portal configuration is the same as in sandbox. Make sure not to select the TestMode option in live. 

Yopur live Gateway URL is: https://payments.comgate.cz/v1.0

Payengine (Concardis)

Payengine - sandbox

To configure your sandbox

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   • API Key: enter the key provided by Concardis. The key is for HTTP API authentication. The key can also be found in the in the Concardis merchant portal (https://merchanttest.payengine.de/) in My Account (API Keys section).
   • Gateway URL: https://apitest.payengine.de/v1
   • Login: enter your merchant Id received from Concardis. It can also be found in the Concardis merchant portal (https://merchanttest.payengine.de/) in My Account. 
   • Password: enter the password provided by Concardis
   • Restrict Full Capture: Payengine only allows one capture request per preauthorization request. Select this option to restrict the capture operation to be for the full amount.
   • Security Token: leave empty
   • Use Merchant Transaction Id: Payengine accepts transaction Ids that are unique and up to 30 alphanumeric characters. If your transaction Ids do not meet this format, leave this option unselected and our orchestration platform will send a suitable transaction Id. Select the option to use your transaction Ids.alphanumeric characters and must be unique. If your transaction Ids do not meet this format, select ‘false'and optile will send a suitable Transaction Id. Select ‘true to use your Transaction Id.

8. Click Continue.

9.Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Concardis. 

10. Add any costs and transaction limits that apply as per the contract.

11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.8B15379

12. Click Finish.

1. Log in to https://merchanttest.payengine.de/login.
2. In your left-hand navigation, click Notifications and then Create Notification.
3. Select URL in the Notification Type.
4. Enter the following URL in the URL field: https://api.sandbox.oscato.com/notification/PAYENGINE/{MERCHANT_CODE}/do.html. Make sure to substitute the <MERCHANT_CODE> with our orchestration platform merchant code. 
5. Expand the Events dropdown and select Select All. 
6. Click Save.

Payengine - live

Follow the sandbox flow for your live environment configuration. Your live contract configuration will have the same data as your sandbox one with the exceptin of your Gateway URL that should be the following on live: https://api.payengine.de/v1.

You need to make updates to the Payengine portal, though. Log in to https://merchant.payengine.de/#!/login (for live) and make sure to update the notification URL with the live domain: api.live oscato.com.

eMerchantPay

eMerchantPay - sandbox

Configure your Merchant portal to test eMerchantPay on sandbox. 

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with eMerchantPay. 
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •  TEST_MODE: for sandbox, enter 1
   •  Gateway URL: https://test.my.emerchantpay.com/service
   •  productType: enter DIGITAL, PHYSICAL or ALL depending on the type of products you sell
   •  support3DSecure: select if you want to use 3D secure for your transactions.
   •  Login: enter your username received from eMerchantPay
   •  Password: enter the password received from eMerchantPay
   •  Security Token: leave empty
9. Click Continue.

11. Add any costs and transaction limits that apply as per the contract.

12. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

13. Click Finish.

• Customer email
• IP address

eMerchantPay - live

Before you go live, update the API Parameters section in your Merchant portal. Make sure you enter 0 for TEST_MODE and the new Gateway URL for your live environment: https://my.emerchantpay.com/service. Note that this the base URL. Depending on the transaction type, a suffix should be added, for example: For CHECKOUT, the complete URL is: https://my.emerchantpay.com/service/order/submit.

Stripe PI

Stripe PI - sandbox

Follow these steps to configure your contract on sandbox:

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Click the Stripe icon to see a dropdown. Select STRIPE-PI.
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   • API Gateway: https://api.stripe.com
   • apiKey: enter the key you've received from Stripe. 
9. Click Continue.
10. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Stripe. 

10. Click Continue.

11. Add any costs and transaction limits that apply as per the contract. 

12. Click Finish.

You have finished configuring the contract. Now, click this contract in the contract list and activate it. 

Now, you need to configure the contract on the Stripe side to receive notifications and for the transaction status to get updated. Notifications are only mandatory for CHARGEBACK. 

1. Go to Stripe.com, and log in to your Stripe account. 
2. In the left-hand navigation, click Developers > Webhooks. 
3. Click + Add endpoint.
4. Enter the following URL in the Endpoint URL field replacing the example with your actual merchant code: https://api.sandbox.oscato.com/notification/STRIPE/<YourMerchantCode>/do.html
5. In the Events to send, click to receive all events.
6. Click Add endpoint.

Now, you can configure your transaction routing in optile to direct your transactions to specific payment providers and methods.

Stripe PI - live

Configure your live aenvironment just in the same way you configured your sandbox as the parameters don't change. 

However, you need to update the Stripe portal:

• update the Webhook endpoint URL to have the live domain instead of the sandbox one: api.live.oscato.com.
• in the main navigation panel toggle the switch from Viewing test data to Viewing live data. 

Kalixa

Kalixa - sandbox

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   • API Gateway: https://api.test.kalixa.com/PaymentRedirectionService/PaymentService.svc/pox/
   • merchantId: enter the unique merchant ID that you have received from Kalixa.
   • shopId: enter the shop ID that you have received from Kalixa.
   • agreeforLiabilityShift (optional): defaults to false. If selected, the liability will be shifted to metchant if, for example, the card is not 3D Secure enrolled. The payment will be completed even if LiabilityShift returned by PSP was 'false'.
   • is3DSec (optional): defaults to false. Select to enable 3D Secure authentication. Note that the debit for the MAESTRO payment method is supported only when 3D Secure is enabled in the contract.
   • isSynchronousCapture (optional): defaults to false. If the box is unselected, the status of transactions is updated to 'debited' when transactions are automatically captured in Kalixa. This could takes up to a few days. If the box is selected, the status of the transactions is updated to 'debited' immediately without waiting automatic capture on Kalixa's side. We recommend selecting this setting. 
   • Login (optional): enter the credentials provided by Kalixa. 
   • Password (optional): enter the credentials provided by Kalixa. 
   • Security token (optional): enter the credentials provided by Kalixa. 
8. Click Continue.
9. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Kalixa. 

10. Click Continue.

11. Add any costs and transaction limits that apply as per the contract. 

12. Click Finish.

You have finished configuring the contract. Now, click this contract in the contract list and activate it. 

You can move on to configuring your transaction routing in optile to direct your transactions to specific payment providers and methods.

Kalixa - live

Klarna

Klarna - sandbox

To set up your sandbox, configure Klarna in your Merchant portal. 

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Klarna. 
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •    Gateway URL: https://api.playground.klarna.com/ (Europe ) and https://api-na.playground.klarna.com/ (USA)
   •    Login: enter your username received from Klarna
   •    Password: enter the password received from Klarna
   •    Security Token: leave empty
   • Klarna allows you to configure the colors of the landing page when your customers from your shop to enter their payment details. Enter the CSS hex colors, for example: #FF9900, in the fields.
9. Click Continue.

11. Add any costs and transaction limits that apply as per the contract.

12. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

13. Click Finish.

Klarna - live

Follow the sandbox guide to set up Klarna in your live environment. Make sure you update the Gateway URL for the live environment to be: https://api.klarna.com/ (Europe ) and https://api-na.klarna.com/ (USA).

You can follow the Klarna checklist to see if you're prepared to go live: https://developers.klarna.com/documentation/klarna-payments/integration-guide/test-go-live/. If you are, notify Klarna to switch you on.

la Caixa

La Caixa - sandbox

To configure your sandbox

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •  Gateway URL: https://localhost
   •  rebatePassword: enter the password received from La Caixa. This is the password to process refunds.
   •  threeDSecureEnabled: select if you support 3d Secure transactions
   •  Login: enter your login received from La Caixa
   •  Password: enter your password received from La Caixa
   •   Security Token: leave empty

   8. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with La Caixa.

   9. Click Continue.

   10. Add any costs and transaction limits that apply as per the contract.

   11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

   12. Click Finish.

   Now, you can also configure routing to direct your transactions to a selected payment provider and payment methods. 

La Caixa - live

Sofort (Gateway)

To set up your Klarna Sofort sandbox and live, you need to do some configuration in Klarna and in the Merchant portal. Alternatively, you can ask Klarna support to configure their end for you. 

You also need to analyze our API calls for the success and abort links to enter in the Klarna portal (for example, they might be http://www.optile.de)

Sofort (Gateway) - sandbox

Configure Klarna

1. Log in to https://www.klarna.com/sofort/.
2. in your left-hand navigation, go to New project > Create project. 
3. Click Gateway project and click Create project.
4. Give your shop a meaningful name and select Own shop system (self programmed) as the shop system.
5. Enter your shop's website. 
6. In the Bank account section, provide your banking details.
7. Enter the success and abort links provided in our API calls and select Automatic redirection.
8. In Payment methods, check the box for Sofort, and select Test mode.
9. Click Save.

10. In the main navigation, go to My projects and click the pencil icon next to your project in the Sofort Gateway section to provide additional details. Copy the project ID to enter in the Merchant portal later on.

11. In the main navigation click API key in the SERVICES section. 

12. Click Generate new API key? > Generate new API key to get a new key. Copy it to enter in the Merchant portal later. 

If you want to test refunds, you need to consolidate them for one currency at a time. You can do multiple refunds with one currency, but before you can do additional refunds with a different currency, you must consolidate the existing refunds. You can't have refund PAIN files with multiple currencies. So, if you want to do a refund with PLN, you must create a PAIN file for that refund and only then can you submit a refund in CHF. Pending is the only state you can get to if you are using non-euro currencies.

1. In the main navigation click Refunds in the SERVICES section. 
2. Click Test refunds > Prepared refunds.
3. Click Save and create file. You will find the file in the Consolidated refunds tab.

Configure your Merchant portal

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Klarna Sofort. 
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •  APIkey: enter the key generated in the Sofort portal.
   •  Gateway URL: https://api.sofort.com/api/xml
   • notificationwithStatus: select if the Sofort account uses a Deutsche Handelsbank bank account. Note that only using a Deutsche Handelsbank account allows for complete refund processing where the orchestration platform is aware of the final state of a refund. The platform can only track the initial submission of the refund with ither banks.
   • projectId: enter the project ID from the Sofort portal.
   • testMode: select for sandbox
   • Login: enter your Sofort portal login
   • Password: enter your Sofort portal password
   • Security Token: leave empty
   • Use Invoice ID as Reason: when selected the invoiceId  parameter is mapped to reason, otherwise longDescription/shortDescription is mapped.
9. Click Continue.

10. Add any costs and transaction limits that apply as per the contract.

11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

12. Click Finish.

Sofort (Gateway) - live

Follow the sandbox configuration to configure your Sofort contract on live. Your Gateway URL and API key in your live environments remains the same however your projectId changes. Make sure you copy the updated one from the Sofort portal to enter in the API Parameters section in your Merchant portal on live. 

Additionally, make sure you unselect testMode in API Parameters in the Merchant portal and in the Sofort portal (under Payment methods). 

MuchBetter

Configure your Merchant portal to test MuchBetter on sandbox. 

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with MuchBetter. 
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •  Gateway URL: https://w.d.muchbetter.com/merchant.
   •  Login: enter your username received from MuchBetter
   •  Password: enter the password received from MuchBetter
   • Security Token: enter the token  received from MuchBetter (for example: MfEKL0b1IcObBpD8cNYHIYt7O76APTte0Hh1Pl4JQjit)
   • Use Dynamic Notification URL: when selected, notification URL in the LIST request will be sent to Muchbetter in every request; this field is optional.
9. Click Continue.

10. Add any costs and transaction limits that apply as per the contract.

11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

12. Click Finish.

Worldpay

To configure your Worldpay contract you need to configure it in the Worldpay portal and in optile. If you have multiple merchant codes from this provider, you need to create a separate contract for each code in optile. 

Start by configuring the contract in Worldpay. 

1. Log in to https://secure.worldpay.com/sso/public/auth/login.html.
2. In the Merchant Code drop-down, select the code for which you'll be configuring your contract. You need to repeat the steps below for every contract you want to configure in optile.
3. In Account > Profile, edit the default XML Password. have the new password at hand, because you'll need it further on in the configuration process. 
4. Go to Integration > Configuration Details and make sure the Capture Delay is set to Off. 
5. Open the Merchant Channel tab to configure how notifications will be sent to our OPG platform. 
6. Configure the Test section of the Merchant Channels as shown below
   
7. In the Address field, enter: https://api.sandbox.oscato.com/notification/WORLDPAY/{MERCHANT_CODE}/do.html, where {MERCHANT_CODE} is your optile merchant code.
8.  In the Merchant Channel Events section, activate all events in the http row. You only need to leave the REFUND_WEBFORM_ISSUED and REFUSED_BY_BANK boxes unselected. 
9. Save your changes. 

10. Change your mode to TEST.
 

Now, configure your contract in optile. 

1. Log in to your merchant portal. 

2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.

• AUTOCAPTURE_ENABLED: select if you want to trigger automated captures of deferred charges. Then the transaction gets authorised immediately. If the setting is off, you might need to wait up to 20 minutes for the capture confirmation. Make sure that this setting is also configured on the Worldpay side.
• MAC-SECRET: Generate the secret on the Worldpay page:  https://secure.worldpay.com/sso/public/auth/login.html, and enter it in optile. 
• MERCHANT-CODE: Enter the code provided by Worldpay.
• MODE: For sandbox, enter TEST.
• Gateway URL: https://localhost
• IS_SYNCHRONOUS_CAPTURE: select if you have AUTOCAPTURE_ENABLED selected. If selected, you receive the authorized notification without waiting for real capture.

8. Click Continue.

9. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Worldpay. 

10. Click Continue.

11. Add any costs and transaction limits that apply as per the contract. 

12. Click Finish.

You have finished configuring the contract. Now, click this contract in the contract list and activate it. 

You can move on to configuring your transaction routing in optile to direct your transactions to specific payment providers and methods.

Paybox

Configure Merchant portal

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   • apiVersion: enter the value provided by Paybox
   • Gateway URL: http://preprod-ppps.paybox.com/PPPS.php
   • identifiant: enter the value provided by Paybox
   • identifiantCastorama: if you're using Castorama as a payment method, enter the value provided by Paybox
   • loginCastorama: if you're using Castorama as a payment method, enter the login provided by Paybox
   • rang: enter the value provided by Paybox. This parameter identifies the contract with the provider.
   • rangCastorama: if you're using Castorama as a payment method, enter the value provided by Paybox.This parameter identifies the contract with the provider.
   • site: enter the value provided by Paybox
   • siteCastorama: if you're using Castorama as a payment method, enter the value provided by Paybox
   • is3DSecure: select if you want your transactions to go through the 3D secure flow
   • Login: enter the value provided by Paybox
   • Password: enter the value provided by Paybox
   • payboxMpiUrl: for sandbox enter: https://preprod-tpeweb.paybox.com/cgi/RemoteMPI.cgi 
   • pciComplianceLevel: enter your compliance level. It depends on your integration type. The compliance level indicates if you have access to sensitive information such as customer card details. 
   •  Security Token: leave empty
   •  transactionReferenceSource: the source to use for Paybox reference. Rnter paymentReference to use short reference; invoiceId - to use merchant invoice Id; transactionId to use merchant transaction Id; requestId to use the orchestration platform long Id (default value). If the selected value is not provided in the LIST request, we fall back to requestId.

8. Click Continue.

9. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Paybox. 

10. Add any costs and transaction limits that apply as per the contract.

11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

12. Click Finish.

Paydirekt

To set up your sandbox, you need to generate API credentials with Paydirekt and configure your Merchant portal.

Get API credentials from the Paydirekt potral 

1. Log in to https://sandbox.paydirekt.de/merchant/#/login.
2. Click on settings icon. 
3. Scroll down the Api-Key-Verwaltung tab. Click Neue API-Key asustellen to generate a new key and secret.
4. Copy the key and the secret and close the pop-up.

Configure Merchant portal

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •  Gateway URL: https://api.sandbox.paydirekt.de
   •  Store API Key: enter the value generated in the Paydirekt portal. 
   •  Store API Secret: enter the value generated in the Paydirekt portal 
   •  Is Compatible Transaction Id: the transaction ID must be unique and maximum 20 characters. Select if yout transaction ID is unique and below 20 characters and you want the transaction rejected if this condition isn't met. Leave unselected if your transaction ID isn't unique and below 20 characters. Then the transaction ID restrictions will be withdrawn. This field is optional.
   •  Login: enter the login from the Paydirekt portal
   •  Password: enter the password rom the Paydirekt porta
   •  Security Token: leave empty
   •  8. Click Continue.

9. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Paydirekt.

10. Add any costs and transaction limits that apply as per the contract.

11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

12. Click Finish.

PayPal

To configure your PayPal contract you need to configure it in the payment orchestration portal and on the PayPal side. 

1. If you haven't got a PayPal account, generate one at www.paypal.com. 
2. Use the same credentials to log in to developer.paypal.com. This is where you'll generate your sandbox data.
3. Sandbox automatically generates your business user account and your first buyer account (personal) for testing. Your business account is marked as Business. Now, select the buyer account, go to Actions > View/edit account and change the password for the buyer account. You will need it when getting redirected to the PayPal page during your testing.
4.  Go back to the business account, go to Actions > View/edit account and open the API Credentials tab. Copy the credentials from the page. You'll need to provide them later on in the Merchant portal.
   
5. If you want to receive currencies other than that of the country you're located in, log back in to www. paypal.com, click the settings cogwheel icon on top of the page and open Seller tools.
6. In the getting paid section, click Update next to Block payments. 
7. Click Yes for the Allow payment to me in the currency I do not hold.

Now, open your Merchant portal to configure your PayPal contract there. 

1. Log in to your merchant portal. 

2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies supported by your contract. If  the  contract  should use  only  a  limited  range  of currencies, deselect All currencies and add the currencies you want to use. The  currencies  you  select  must  match  the  currencies  in  your contract with PayPal. currencies, you will need to deselect ‘All Currencies' and add the currencies you want to use. Note, that the currencies you select here must match the currencies in your contract with PayPal.
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.

• CUSTOMER_LOGIN_ENDPOINT_URL: https://www.sandbox.paypal.com/webscr
• Gateway URL: https://api-3t.sandbox.paypal.com/nvp
• ALLOW_GIROPAY: a Germany-specific payment option. Leave blank, if you don't specifically want this option; this field is optional
• ALLOW_CHANGE_SHIPPING_ADDRESS: if selected, a customer will be able to change the shipping address on PayPal side; this field is optional
• BLOCK_STANDALONE_CHARGE: if selected then in case customer registers a MIT transaction with a merchant, and the registration attempt fails with PayPal, then the adapter will no longer trigger a charge attempt; this field is optional
• CLIENT_ID: enter "sb" for sandbox. PayPal REST client ID. This identifies merchant's PayPal account, and determines where transactions are paid to. 
• CONNECTION_TIMEOUT: Connection timeout for Paypal's communication (360000ms = 6 minutes by default); this field is optional
• DISTINGUISH_PENDING_REASON: If selected, you'll be getting more information about why a transaction is pending; this field is optional
• INDIVIDUAL_BILLING_AGREEMENT_DESCRIPTION: if selected, the adapter sends individual payment description for each transaction to a PayPal's parameter payment.longReference.verbose; this field is optional
• INSTANT_PAYMENT_ONLY: if selected, it forces the custimner to select instant payment methods; this field is optional
• JAVASCRIPT_INTEGRATION: if selected, you can use PayPal's 'checkout.js' so that the PayPal window is generated as a pop up/widget not a full page redirect; this field is optional
• NEGATIVE_TESTING: select if you want to test negative outcomes on sandbox and make sure you can handle errors (for example business declines such as insufficient funds);this field is optional
• PAGESTYLE: enter a custom style for the payment page; this field is optional
• PAGE_BUTTON_COLOR:  "Gold" by default; this field is optional
• PAGE_BUTTON_LOCALE: for example de_DE, en_US;this field is optional
• PAGE_BUTTON_SHAPE: 'rect' by default;this field is optiona;
• PAGE_BUTTON_SIZE: 'small' by default; this field is optional
• PAGE_ENVIRONMENT: "sandbox" by default; this field is optional
• PAGE_FRAUD_SOURCE_ID: The source ID required for Fraudnet library; this field is optional
• REQUEST_BILLING_ADDRESS: if selected, PayPal returns a billing address; this field is optional and must also be set on the PayPal side
• USE_ESSENTIAL_DESCRIPTION: select if you would like to use essential description as billing reference (if it is present and the short description exceeds the number of characters permitted by PayPal); this field is optional
• USE_TRANSACTIONID_AS_INVNUM: select if you want to use TransactionId as InvoiceId when InvoiceId is not provided;  this field is optional

1. Create a demo shop using our hosted payment page. 

could generate a test shop with the optile hosted paymen

OceanPayment

Configure Merchant portal

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •  Gateway URL: https://secure.oceanpayment.com/gateway/
   •  queryUrl: https://query.oceanpayment.com/. This base URL is used for refunds.
   •  account: enter the number provided by OceanPayment
   •  isTest: select for sandbox
   •  Login: enter your username provided by OceanPayment
   •  Password: enter the password provided by OceanPayment
   •  secureCodeApp: enter the secure code for the WeChat App method provided by OceanPayment. Secure code is required (and unique) for each payment method. It's used by OceanPayment to determine which payment method is requested.
   •  secureCodeMiniProgram: enter the secure code for the WeChat Mini Program method provided by OceanPayment. Secure code is required (and unique) for each payment method. It's used by OceanPayment to determine which payment method is requested.
   •  secureCodePcRedirect: enter the secure code for the WeChat Payment PC (Redirect) method provided by OceanPayment. Secure code is required (and unique) for each payment method. It's used by OceanPayment to determine which payment method is requested.
   •  Security Token: leave empty
   •  terminalApp: enter the terminal for the WeChat App method provided by OceanPayment. Terminal is required (and unique) for each payment method. It's used by OceanPayment to determine which payment method is requested.
   •  terminalMiniProgram: enter the terminal for the WeChat Minin Program method provided by OceanPayment. Terminal is required (and unique) for each payment method. It's used by OceanPayment to determine which payment method is requested.
   •  terminalPCRedirect: enter the terminal for the WeChat Payment PC (Redirect) method provided by OceanPayment. Terminal is required (and unique) for each payment method. It's used by OceanPayment to determine which payment method is requested.
   •  useInvoiceIdAsOrderNumber: if selected,  invoiceId parameter is mapped to Oceanpayments orderNumber, otherwise merchantTransactionId is mapped.

8. Click Continue.

9. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with OceanPayment. 

10. Add any costs and transaction limits that apply as per the contract.

11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

12. Click Finish.

Mandatory paramaters

• Customer email is required for all payment methods
• The field pay_userId (described as "Consumer ID card") should be passed under customer?number in the LIST request
• ClientInfo ?ip address is required for mobile payment methods -WECHATAPP, WECHATMINIPROGRAM (Not necessary for SANDBOX due to limitations)
• The Consumer openid must be passed in the account ?number field in CHARGE request for the WECHATMINIPROGRAM payment method. You need to receive the Consumer openid from WeChat. (Not necessary in SANDBOX due to limitations). For details, see  https://developers.weixin.qq.com/doc/oplatform/en/Third-party_Platforms/Mini_Programs/WeChat_login.html
• Customer name should be passed as either Account ? holderName or in Customer ? Name
• To differentiate between the 3 payment methods, we suggest using Divisions. Division is a mandatory parameter in the LIST request which helps determine the payment method to be displayed.

Mobile app payment

• WECHATAPP and WECHATMINIPROGRAM payment requests will return the parameters necessary for the merchant to initiate a WeChat mobile application payment.  The necessary parameters will be provided in the CHARGE response field:  providerResponse.
• WECHATAPP will return the following parameters: partnerid, appid, package, timestamp, noncestr, and prepayid
• WECHATMINIPROGRAM will return the following parameters: timestamp, noncestr, and package

Allowlisting

Make sure to request that OceanPayment allow-list the following domains:

• api.live.oscato.com
• resources.live.oscato.com
• api.sandbox.oscato.com
• resources.sandbox.oscato.com

Ogone

To set up your sandbox, you need to configure the Ogone portal and enter details in. yoour Merchant portal. Make sure that you copy the following details from the Ogone portal into the Merchant portal: Sha1InSignatureAt, Sha1OutSignatureAt, PSPID. 

Ogone configuration

1. Log in to https://secure.ogone.com/Ncol/Test/BackOffice/login/index.
2. Go to Configuration > Technical information > Global security parameters.
3. Set the Hash algorithm to SHA-1 and the Character encoding to UTF-8. Save your changes.
4. Go to Configuration > Technical information > Data and origin verification.
5. Click on VISIBLE for the two SHA-IN pass phrases and make sure they are the same. Copy the phrase for later.
6. Go to Configuration > Technical information > Transaction feedback.
7. Add the following URL to Accepturl, Declineurl, Exceptionurl and Cancelurl: https://api.sandbox.oscato.com/decision/OGONE/<YOURMERCHANT>/do.html. Make sure you replace <YOURMERCHANT> with your orchestration platform merchant code.
8. (optional) If you use any redirect payment methods, make sure to check the box: "I would like to receive transaction feedback parameters on the redirection URLs."
9. In the Direct HTTP server-to-server request section, select Online as timing and POST as the request method. Additionally enter the URL from step 7 in the two merchant post-payment page fields.

10. In the Dynamic e-Commerce parameters move the following parameters from Available to Selected: ACCEPTANCE,  AMOUNT,  BRAND,  CARDNO,  CN,  COMPLUS  ,CURRENCY, ED, IP, MANDATEID, NCERROR, ORDERID, PAYID, PAYMENT_REFERENCE, PM, SIGNDATE, STATUS, TRXDATE 

11. In the Security for request parameters, click VISIBLE to see the SHA-OUT pass phrase and copy it for later.

12. In the Direct link - Dynamic parameters section move the following parameters from Available to Selected: ACCEPTANCE,  AMOUNT,  BRAND,  CURRENCY, MANDATEID,   NCERROR,   NCERRORPLUS,   NCSTATUS,   ORDERID,   PAYID,   PM, SIGNDATE, STATUS, VALID 

13.Save your changes.

14. Go to Configuration > Create production account and copy the PSPID. You'll need it for your Merchant portal.

Merchant portal configuration

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Ogone. 
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •  directLinkMaintaintUrl: https://ogone.test.v-psp.com/ncol/test/maintenancedirect.asp
   •  directLinkURL: https://ogone.test.v-psp.com/ncol/test/orderdirect_utf8.asp
   •  Gateway URL: https://ogone.test.v-psp.com/ncol/test/orderstandard_utf8.asp
   •  merchantPsp: enter the PSPID value you copied from Ogone
   • sha1InSignatureAt: enter the SHA-IN value copied from Ogone
   • sha1OutSignatureAt: enter the SHA-OUT value copied from Ogone
   • 3DRedirectURL: if you support 3D secure transactions, enter: https://ogone.test.v-psp.com/ncol/test/Test_3D_ACS.asp
   • isGermanAccount: leave the field empty
   • Login: enter the login you use for the Ogone portal
   • Password: enter the password you use for the Ogone portal
   • QueryURL: https://ogone.test.v-psp.com/ncol/test/querydirect.asp
   • Security Token: leave the field blank
   • sofortBrandCountry: if your contract is for "Sofort Überweisung (DE)", entre "DE". If not, leave the field empty.
   • support3DSecure: select, if you support 3D Secure transactions
   • useMerchantId: select if you want your transaction ID to be sent to Ogone. Make sure it's always a unique value for each transaction and that it is in line with Ogone's requirements (maximum 40 alphanumeric characters).
9. Click Continue.

11. Add any costs and transaction limits that apply as per the contract. 

12. Click Finish.

You have finished configuring the contract. Now, click this contract in the contract list and activate it. 

You can move on to configuring your transaction routing in optile to direct your transactions to specific payment providers and methods.

SecureTrading

To configure your SecureTrading sandbox environment, you need to configure it in SecureTrading and in your Merchant portal. 

SecureTrading:

1. Log in to https://myst.securetrading.net with the credentials you received from the provider. 
2. Go to Sites and click on the test site link. Make sure you're clicking the correct site because your user might be linked to several sites. It's a good idea to copy the sire reference as you'll need it for the Merchant portal.
3. Click Site users.
4. Click Edit next to the Webservices user and enter your New password. Store it for later to provide in the Merchant portal.
5. In the Valid IP/Network(s) enter: 213.95.26.76 and save your changes.
6. If you want to see what account features are linked to your account, go back to sites, click the site link and click Account.

Now configure the Merchant portal

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with SecureTrading. 
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •   Gateway URL (sandbox): https://webservices.securetrading.net:443/xml/
   •   sirereference: enter the site reference from the SecureTrading portal
   •   defaultRegistrationCurrency: during standalone registration we register the card using a token amount and then cancelling the charge. To do this we use the default currency of EUR. To change the currency, enter another currency.
   • is3DSecure: select if you support 3D Secure transactions
   •   Login: enter your username from SecureTrading
   •   Password: enter the password you entered for the Webservices user in the SecureTrading portal
   •   Security Token: leave empty
9. Click Continue.

11. Add any costs and transaction limits that apply as per the contract.

12. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

13. Click Finish.

SaferPay

You need to configure your SaferPay sandbox in your Merchant portal using credentials you received from the provider.

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with SaferPay. 
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   • customrId: enter the first part of the AccountID (for example: 123123-12345678)  provided by SaferPay
   • Gateway URL (sandbox): https://test.saferpay.com/api
   • Agree For Liability Shift: when selected, payment will be completed even if LiabilityShift returned by Saferpay was false; this field is optional
   • Login: enter the credentials provided by SaferPay
   • Password: enter the credentials provided by SaferPay
   • Security Token: leave empty
   • Use Invoice ID as Order ID Charge: when selected, invoiceId is passed as Saferpay orderId parameter in the CHARGE requests. When unselected, merchant transactionId is used instead; this field is optional
   • Use Invoice ID as Order ID Refund: when selected, invoiceId is passed as Saferpay orderId parameter in the REFUND requests. When unselected, merchant transactionId is used instead; this field is optional
9. Click Continue.

11. Add any costs and transaction limits that apply as per the contract.

12. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

13. Enter the POS terminal ID. Saferpay provides one or more terminals for you based on your contract with them. All the transactions should be processed through these terminals. Specify all the  terminal ID's provided to ensure transactions are processed properly.

14. Click Finish.

SEPAexpress

To set up your sandbox, configure SEPAexpress in your Merchant portal.

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with SEPAexpress. 
6. Select the methods and add the countries in which these methods will be available as per your contract. Note that there are two payment methods available for SEPAexpress: SEPA (for all European Union countries, except the United Kingdom) and BACS (only for the United Kingdom) If you want to trade in the United Kingdom and an EU country you need to activate both: BACS and SEPA.  If you want to trade worldwide, select Global fior both methods.
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   • authenticationUrl: https://id.sepa.express/connect/token 
   • Gateway URL: https://sandbox.sepa.express
   • isTest: select this option for sandbox
   • pspId: enter the ID you received from SEPAexpress. If you haven't received any, contact our support.
   • isCancelEnabled: when selected, you to cancel a payment that is in the pending state.You can only use this setting if it's enabled with SEPAexpress for your contract.
   • lastReconciliationEntryId: enter the reconciliation entry ID from which to start reconciliation processing. Only applicable for SEPA Express PSP contracts.
   • Login: enter theb4pId value provided by SEPAexpress ( for example: Z1000001)
   • normalizeMandateReference: SEPAexpress doesn't allow non-alphanumeric characters in the mandate reference. When selected, all special characters (non-alphanumeric characters) will be deleted from the mandate reference. If yu select this parameter, it will change the mandate reference value if it has non-alphanumeric characters. This field is optional.
   • Password: you can leave the field empty
   • reconcilliationCount: you can leave the field empty
   • Security token: you can leave the field empty.

10. Click Continue.

11. Add any costs and transaction limits that apply as per the contract. 

12. Enable any additional settings you need. Enabling additional settings will only take effect if these features are offered by the provider and implemented by our orchestration platform team.

12. Click Finish.

You have finished configuring the contract. Now, click this contract in the contract list and activate it. 

You can move on to configuring your transaction routing in optile to direct your transactions to specific payment providers and methods.

PayU

To set up your sandbox, you need to configure the PayU portal first. When configured, PayU should provide you with contract AppID and API keys. When yu have those, you can configure the Merchant portal. 

PayU configuration

1. Log in to the PayU portal using your credentials (https://control.paymentsos.com/login).
2. In the left-hand navigation, go to Account > Webhooks.
3. Click Create a Webhook Endpoint.
4. Enter the endpoint's URL: https://api.sandbox.oscato.com/notification/PAYU/<MERCHANT_CODE>/do.html replacing the <MERCHANT_CODE> with the one you got from the orchestration platform. If you haven't received one, contact our support. 
5. Toggle on Update for the following operations: Authorization, Capture, Charged, Refund, Void.
6. In the Associated Business Units, select the countries in which you'll be operating. 
7. Select the latest webhook version.
8. Click Create.
9. Contact PayU for contract AppID and API keys. When you have those, you can configure the Merchant portal.

Merchant portal

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •  customrId: enter the first part of the AccountID (for example: 123123-12345678)  provided by SaferPay
   •  AppId: enter the ID provided by PayU, for example: net.optile.russia
   • Environment: for sandbox, enter: test
   • Gateway URL (sandbox): https://api.paymentsos.com/
   •  Private key: enter the API provided by PayU, for example: 8e054926-3be5-4071-90dc-87d12ddf5746
   •  Login: enter the credentials provided by PayU; this field is optional
   •  Password: enter the credentials provided by PayU; this field is optional
   • Public key: enter the public API key provided  by PayU, for example: 81742180-ef2e-487a-b223-fd877de4a6ce. If you didn't receive this key, leave the field empty.
   •  Security Token: leave empty
8. Click Continue.
9. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with PayU. 

11. Add any costs and transaction limits that apply as per the contract.

12. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

14. Click Finish.

Telecash

Configure your Merchant portal to test Telcash on sandbox. 

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Telecash. 
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   • certificate: enter the certificate provided by Telecash
   • certificatePwd: enter the certificate password provided by Telecash
   • Gateway URL: https://test.ipg-online.com/ipgapi/services
   • storeId: enter the store ID provided by Telecash
   • 3DS v2 supported: select if you want to use 3S v2 for your transactions.
   •      In  sandbox, there  are  two  credit  cards,  which  are  registered  for  3D Secure. If you want to test a failed authentication, click Cancel in sandbox  to get Authentication failed. Make sure you don't enter a wrong password as this will lock the card.
   • The card details are as follows: Visa: 4035874000424977
   •                                                         Mastercard: 5426064000424979
   •                                                         Expiry date: any date in the future
   •                                                        CVV: a 3ndigit number
   •                                                       Password for 3D secure: secret3
   •        Telecash doesn't support customer ABORT during 3D Secure authentication. If during 3D Secure Authentication, a customer clicks the Cancel button, the response from Telecash is: "SGS-005101: Transaction declined. 3D Secure authentication failed". There is no differentiation between 'aborted'   or   'wrong   password'.  This way both '3D   Secure Authentication Failed' is valid for both scenarios.
   •     Login: enter your username received from Telecash
   •     Password: enter the password received from Telecash
   •     Security Token: leave empty
9. Click Continue.

11. Add any costs and transaction limits that apply as per the contract.

12. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

13. If you have POS terminals in the contract, enter the ID so that transactions are processed successfully. 

14. Click Finish.

Wirecard

To configure your sandbox

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Wirecard. 
6. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
7. Click Continue. 
8. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   • businessCaseSig: enter the Business Case Signature you received from Wirecard
   • demoMode: select for sandbox
   • Gateway URL: https://c3-test.wirecard.com/secure/ssl-gateway
   • Login: enter your HTTPS Username received from Wirecard
   • Password: enter your HTTPS Password received from Wirecard
   •  Security Token: leave empty
   • support3DSecure: select if you support 3d Secure transactions
   • support3DSecurev2: select this option and support3DSecure to support 3D Secure 2 transactions
   • This is all the data you need to enter for sandbox as you cannot test chargebacks there. For automated processing of chargebacks, contact Wirecard support (support@wirecard.com) and request SFTP access to Reconciliation Files.Provide to Wirecard support the IP address of the orchestration platform open payment server (production). The external IP of the production server is the following: 195.27.175.132 (port 22). The support should provide you with the SFTP reconUser to enter in the Merchant portal.step, and skip the following section.
9. Click Continue.

11. Add any costs and transaction limits that apply as per the contract.

12. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

13. Click Finish.

Twisto

Configure the Twisto portal

1. Log in to https://eshop.twisto.cz/login.
2. In the right-hand navigation click Integration. 
3. Copy the Public key and the Secret key for the Merchant portal. 
4. In the Webhook URL field, enter https://dev.oscato.com/twisto.
5. In the Allowed e-shop domains, click Add domain and add your e-shop domain, localhost, resources.sandbox.oscato.com, oscato.com to be allow-listed. This will enable proceeding with credit check. All front-end domains must be white-listed. 
6. If you integrate the orchestration platform natively, read the JS section. Twisto's front end logic requires a special JS library  to be added to your checkout page.

Configure the Merchant portal

1. Log in to your merchant portal. 
2. In the left-hand navigation, click Provider Contracts.
3. Click + New Contract.
4. Search for the provider and click on the provider's icon to select it. 
5. Select the methods and add the countries in which these methods will be available as per your contract. If the methods will be available in all countries, select Global. 
6. Click Continue. 
7. In the API Parameters section, enter the required data. You can leave the remaining fields blank.
   •  Gateway URL: http://localhost
   •  publicKey: enter the key copied from the Twisto portal
   • secretKey: enter the key copied from the Twisto portal
   •  Login: enter your login from the Twisto portal
   •  Password: enter the password from the Twisto portal
   •  Security Token: leave empty
   •   Shop logo Url: enter the URL to your shop's logo that will be displayed  at  the  top  of  the  order  page  in MyAfterPay.

8. Click Continue.

9. Select the currencies this contract will use, or leave All currencies selected. If the contract should only use a limited range of currencies, add the currencies you want to use. The selected currencies must match the currencies that you have activated with Twisto. 

10. Add any costs and transaction limits that apply as per the contract.

11. Select any additional settings. Enabling the additional settings will only take affect if these features are provided by the provider and are implemented by our payment orchestration team.

12. Click Finish.