Skip to main content
This topic contains Reseller (Service Provider) connectivity best practices recommendations.

​
Connectivity

Configuration Expectations All configuration expectations should be reviewed and agreed upon by both software architects and the DevOps team. Configuration Expectations The following two Reseller (Service Provider)-to-MarketONE connection methods can be used.
  1. Public Interface. This is the recommended method.
  2. AWS Direct Connect. This method a direct Layer 2 (L2) link to the customer site from AWS.
Note: The MarketONE ↔ Reseller (Service Provider) connectivity plan should be reviewed during the initial contact negotiations, and during the final contract sign-off. Some of the solutions may require extra budgeting considerations.

​
AWS Connectivity

Note: Please refer to Building a Scalable and Secure Multi-VPC AWS Network Infrastructure for AWS Connectivity best practices recommendations.

​
BSS Idempotency

It is possible that a non-idempotent BSS (with the enterprise service bus (ESB) in front, and multiple legacy systems in the backend) might take a very long time to respond to a transaction. In this situation, if a Merchant submits a transaction, and is not notified in a reasonable amount of time that it has been successfully processed by the BSS, the Merchant might conclude that the transaction has failed. In response to this possibility, a Merchant might then retry the same transaction later, only to have the non-idempotent BSS return a duplicate transaction error. To avoid this situation it is strongly recommended that the Reseller (Service Provider) BSS be idempotent. This way even if the BSS receives a transaction multiple times from a Merchant, it will always return the same outcome.

​
Retry Mechanism

Requests that come into MarketONE are validated by an API key. Occasionally the validation of the key (as part of the SSL handshake) results in a timeout, thereby returning one of the following 5xx errors back to the client: Note: To overcome these occasional connection timeouts, MarketONE recommends that you implement a retry mechanism. Please refer to the AWS Timeouts, Retries, and Backoff with Jitter page for further information.