Access
List who can view transactions, issue refunds, download reports and change payout details. Sharing a password is not an access model. It is refused.
Responsibilities
A payment partnership is mostly a set of responsibilities. Compensation is one line in that set, not a substitute for the rest.
List who can view transactions, issue refunds, download reports and change payout details. Sharing a password is not an access model. It is refused.
Name the legal entity that receives funds and the account they land in. If that entity is not the seller, the difference has to be permitted by the processor, not just agreed privately.
Say what the customer sees at checkout, on the receipt and on the card statement. The seller they see should be the seller they have.
Name who decides a refund, who has the access to make it, and whose balance it comes from.
Name who gathers evidence, who responds, and by when. A dispute does not become someone else’s problem by silence.
Name who carries a held reserve, a lost dispute, a scheme fine or a delayed payout. The provider’s terms still apply on top of any private split.
Say what ends the relationship, what happens to unfulfilled orders, and how access is removed. Unrestricted exit is not assumed.
A new product, website, owner, country, payout beneficiary or processing pattern is a new question, not a small edit.
A private contract does not remove the processor’s rules. A completed questionnaire does not assign these duties. They are assigned in the agreement, which is not executable in this preview.
Read the longer note