Skip to main content

Environments

Overview​

Ensenta provides access to two environments – UAT and Production (PROD). Within each environment, Mobile Vendors will receive multiple unique Partner IDs (see StartSession) to connect to specific setups for certification, business testing, and production.

ENVIRONMENTPARTNER ID TYPEPURPOSE
UATIntegration CertificationThis Partner ID will be the first one provided and is intended for the Technical Partner to use for developing the application and certifying the integration with Ensenta.

Transactions coming to this setup should come from a non-production environment. The purpose of this Partner ID is to test for required base functionality and to complete the Integration Certification. This Partner ID should not be used for business rules testing. Do not use live production data and/or check images in this environment.
UATBusiness TestingThis Partner ID will be provided upon completion of the Integration Certification and will be configured to match business rules and deposit policies defined by the Financial Institution.

Transactions coming to this Partner ID should come from a non-production environment. This Partner ID should be used for business rules testing. Do not use live production data and/or check images in this environment.
PRODProductionThis Partner ID will be provided upon completion of Business Testing. Business rules signed off in UAT will be copied over to the PROD Partner ID.

Transactions coming to this Partner ID should come from a production environment.

Service URLs​

The following sections provide the service URLs, public IP address, and ports for the User Acceptance Testing (UAT) and Production environments.

The WSDL and XSD files for UAT and Production can be found in the Downloads section of this portal.

User Acceptance Testing (UAT) Environment​

The following URLs should be targeted in UAT, for Integration Certification and Business Testing:

SERVICEURLIP/PORT
SSOhttps://webdeposit.test.ensenta.com/PartnerAPI/SingleSignon/PartnerSSORequest3.svcUAT/Staging Public IP:
34.49.197.56
Port: 443
Deposithttps://webdeposit.test.ensenta.com/PartnerAPI/PartnerDepositRequest3.svcUAT/Staging Public IP:
34.49.197.56
Port: 443

Production and DR Environments​

The following URLs should be targeted in Production and DA:

SERVICEURLIP/PORT
SSOhttps://webdeposit.ensenta.com/PartnerAPI/SingleSignon/PartnerSSORequest3.svcProd and DA Public IPs:
34.8.185.145
52.230.228.247
Port: 443
Deposithttps://webdeposit.ensenta.com/PartnerAPI/PartnerDepositRequest3.svcProd and DA Public IPs:
34.8.185.145
52.230.228.247
Port: 443

Service Data Limits​

There are data limits for how large a request to the Ensenta Partner API3 services can be; exceeding the data limits outlined below will result in an HTTP 413 Payload Too Large.

  • All methods within the SSO service (PartnerSSORequest3.svc) are limited to a request size of 49,152 bytes.

    note

    The data limit’s main potential impact in the SSO service is that there is an upper limit to how many possible eligible accounts for an end-user can be sent in the StartSession request. We can’t provide an exact number of accounts that can be supported within your integration as it depends on the specific details sent in your integration’s payload for StartSession, but 120 accounts are generally observed as the upper limit.

  • All methods within the Deposit service (PartnerDepositRequest3.svc) are limited to a request size of 30,000,000 bytes.

Timeouts​

For security reasons, Ensenta enforces two timeouts:

  1. Inactivity Timeout: The session will be terminated after 15 minutes of no activity from the application server.
  2. API Reponses Timeout: The response will timeout if an API response is not returned within 45 seconds (API responses with longer average response times are generally four to five seconds, with the majority of Ensenta’s API response times being less than one second).