Merchant Agreement - Historical

Applied By Justis R: Sep 1, 2019 at 7:09 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.


The provider is responsible for ensuring that they have ownership of whatever item it is that they’re offering. Cracked or stolen content, in part or in full, will never be permitted under any circumstances. It matters not how many times the product has traded hands since it was stolen, nor how long it has been since it was stolen, nor how much the product has changed. If a provider knowingly or unknowingly transacts a product that they did not own full rights to transact, then they owe the receiver of that item a full refund or equal compensation.


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.


The provider of a product is responsible for informing the receiver of every dependency which their product depends on, that the receiver could potentially be lacking. This needs to be communicated prior to the transaction’s initiation. A dependency could be public software, paid software, a website that must be online, an externally hosted file that needs to be public, a HWID or other activation key, etc.


If no deadlines are provided, then each party has seven days to fulfill their responsibilities. If one party must wait on the other before they are able to attempt to fulfill their responsibilities, their seven days will start when the party they are waiting on is no longer impeding their ability to fulfill them. New deadlines may be mutually agreed upon after the transaction has begun. Agreeing to new deadlines means the old deadlines no longer have any relevance, even if they had been exceeded prior to the new arrangements.


Participants making payments are not responsible for covering the transaction fees applied by whichever payment processor the participants decide to use. When a price is agreed upon, that money figure is what is sent, not necessarily what is received. Moreover, the person making the payment is responsible ensuring that their banking accounts are secure, and unauthorized chargebacks will not be filed.​

Most importantly, each participant in a transaction is responsible for providing what was mutually agreed. Failure to do so, or to provide the required compensation will be considered scamming and result in a permanent ban from our platform.

Stay safe, deal on site, and respect your fellow merchants.
Your MC-Market staff team​