Merchant Agreement - Historical

Applied By Justis R: Sep 1, 2019 at 5:03 AM

Merchant Agreement

Merchant Agreement
NOTICE - This is a draft. Contents are not “Official” writings.
When a transaction between members of our platform deteriorates into a dispute and requires involvement by our staff team to resolve, our role is no more or less than to enforce that each participant of the transaction upholds their responsibilities.

However, these disputes most often occur as a result of miscommunication, rather than malicious intent, and so it is in fact a lack of mutual understanding regarding the responsibilities that each participant is bound by which causes deals to fall through.

Even if a full list of responsibilities isn't verbally discussed, many must fall on either one party or the other. This Merchant Agreement was created to outline the responsibilities that each transacting party will be bound to if they fail to communicate and agree upon a differently assigned set of responsibilities for MC-Market to enforce.

Publicly outlining these responsibilities ensures that the staff team’s enforcement of a transaction is both reliable and transparent. We would like for every participant in a transaction to engage only while fully aware of what to expect from their transaction partner(s), and what will be expected of them in return.

These responsibilities were decided upon with the best interests of the entire community in mind, as well as what is most commonly assumed by the majority of transaction participants where communication was not used to verify that those assumptions were mutual. These responsibilities may not necessarily always be what’s most desired by you and your transacting partner(s), so it is strongly encouraged that you communicate with them and ensure that everyone’s both on the same page, and satisfied with the arrangement.

Any responsibilities mutually agreed upon within the context of a transaction which conflict with what’s written here will always take precedence for that transaction.

The provider of the product is responsible for ensuring that it is compatible with the product receiver’s platform. Any information the provider needs to ensure that they can deliver a compatible product is the provider’s responsibility to ask for. (e.g java version, server software, server version, etc) If there are any limitations to the product’s compatibility, that needs to be made known to the receiver prior to the transaction’s initiation. If there are no limitations made known to the receiver by the provider, then the receiver should be able to assume, that it will work for them.​


If the receiver loses their functioning product due to a security risk which existed prior to receiving the product, and which was not communicated to them by the provider prior to the transaction, the provider is held responsible. If the provider communicates all of the security risks prior to transaction, and the receiver accepts the product regardless, then the receiver accepts responsibility for the product’s security where those risks are concerned. If one of those risks causes the receiver to lose their product after having received it, the provider will not be held responsible.


If a receiver of a usage license is not explicitly given permission to redistribute the product or re-sell their usage license, then the license is non-transferrable, and the receiver maintains full responsibility over all of their downloads. If one of the receiver’s copies enters the hands of a person who does not have a usage license, compensation worth one license sale per unlicensed person that obtains the copy is owed to the owner of the product.​

Your MC-Market staff team​