Common Principles (Receipts & Disclosures)

This page sets out the principles that apply to all MoneyGram receipt categories (Send, Receive, Amend, Cancel) and to the disclosures they carry. Read this page first: which variants of the receipt content apply to your integration depends on your operating model, your markets and your channel. The category pages define what each receipt must contain; this page defines how those requirements vary and where shared content comes from.

Item	Principle / Disclosure text	Requirement
C1	Operating model. Before implementing any receipt, establish which model applies to your integration: (a) MG Agent — you act under MoneyGram's license (MoneyGram Payment Systems, Inc. is the regulated provider); (b) Own-license partner — you are the regulated payment service provider for the customer, and the transfer is processed through the MoneyGram network; (c) White-label / MoneyGram-as-a-Platform — the applicable structure is defined in your agreement. Your operating model determines the provider identification, Terms & Conditions reference, privacy disclosure and contact details on every receipt category. If you are unsure which model applies, confirm with your MoneyGram integration manager before certification.	All models, all categories. Required reading — the model determines which variant of every model-dependent item applies. The model is confirmed during onboarding and recorded in the certification file.
C2	Provider identification — MG license model: “This money transfer service is provided by MoneyGram Payment Systems, Inc., a corporation organized under the laws of Delaware, USA, with its principal office at 1550 Utica Avenue South, Minneapolis, MN 55416, United States. MoneyGram Payment Systems, Inc. is duly licensed as a money transmitter (NMLS ID: 898432).” other language versions per C7; + additional local licensing details where the market requires them	MG Agent / MPSI model, all categories. Required on all receipts, verbatim or in equivalent substance.
C3	Provider identification — own-license model: “[Partner name] is the regulated payment service provider for this transaction. The international money transfer is processed via the MoneyGram network. [Partner name] Terms & Conditions and the applicable MoneyGram Terms & Conditions apply.” (adapted to the partner's legal name and structure)	Own-licence partners, all categories. Required in substance: the receipt must (i) name the partner as the regulated provider, and (ii) disclose that the transfer is processed via the MoneyGram network. MoneyGram's remaining content standards operate as recommendations for own-license partners, except where stated otherwise on the category pages.
C4	Provider identification — white-label / MoneyGram-as-a-Platform: “[Regulated entity name] is the provider of this money transfer service. The service is operated on the MoneyGram platform and transfers are processed through the MoneyGram network.” (adapted to the arrangement — the regulated entity and role allocation follow the agreement)	White-label / MPS structures, all categories. Required in substance: the receipt must identify the regulated entity for the customer relationship and disclose MoneyGram's platform/network role, without implying the transaction is conducted solely by either party. Partners operating under the “white label” model must be verified by MoneyGram on a case-by-case basis.
C5	Terms & Conditions reference by model: MG license — the receipt references MoneyGram's Terms and Conditions (see the category pages for the acknowledgement wording). Own-license — the partner's Terms and Conditions are primary; a reference to the applicable MoneyGram Terms and Conditions must also appear (see C3). White-label / MPS — per C4. On receive receipts, the reference is informational only — the receiver is not the contracting party and no acceptance formula may be used.	All models, all categories. Required. The T&C reference must identify the correct contracting party for the customer; an acceptance formula may only be used where the customer holding the receipt is the contracting party.
C6	Data controller identification: MG license — MoneyGram Payment Systems, Inc. is identified as the data controller (see the category pages for the baseline text). Own-license / white-label — where the partner processes the customer's personal data as an independent controller (registration, KYC, customer relationship), the receipt must identify both controllers and their respective processing purposes, and link both privacy notices: “[Partner name] is the data controller of registering you as a customer, verifying your identity, managing its customer relationship with you, and meeting its own applicable legal and regulatory obligations in connection with this money transfer under its Privacy Notice [link]. MoneyGram Payment Systems, Inc. (1550 Utica Avenue South, Minneapolis, MN 55416, United States), and, where applicable, the additional MoneyGram data controller identified for your country and service in MoneyGram’s Data Controller List [link: https://www.moneygram.com/us/en/data-controllers-list] are data controllers of your personal data for processing and completing this money transfer through MoneyGram’s network, preventing financial crime and meeting its applicable legal and regulatory obligations under the MoneyGram Global Privacy Notice [link].”	All categories. Required in the variant matching the actual controllership. The controller(s) named on the receipt must match the actual allocation of data protection responsibility in the integration; a receipt naming the wrong controller fails review.
C7	Language rules: (a) the receipt must be available in a language the customer can reasonably be expected to understand — as a baseline, an official language of the market where the customer transacts (send side: send country; receive side: receive country), or a language selectable by the customer, in addition to English; (b) United States: where the transaction flow is presented in Spanish, the Pre-Payment Disclosure and the receipt must be provided in both English and Spanish; where the flow is English-only, English-only documents suffice; (c) market-specific language obligations prevail over this baseline; MoneyGram supplies or approves required language versions during onboarding.	All categories. Required. Language variants of mandated disclosures must be translations of the approved English master; translations are subject to the same review as the master.
C8	MoneyGram-generated receipts vs agent-built receipts: where your integration uses MoneyGram-generated receipts, you must render the exact, complete receipt data (MIME) returned by the API, without modification, truncation or re-composition; MoneyGram controls the non-transaction text. Where you build your own receipts, the category pages on this Portal define the required content, and your receipt is subject to review and approval as a prerequisite of certification. State in your certification file which approach each receipt category uses.	All categories. Required. Mixing the two approaches within one category (e.g. rendering MG receipt data with local edits) is not permitted.
C9	Service-type elements: depending on the service option, the receipt must include — Cash pick-up: availability statement using “MoneyGram agent or partner location” (do not imply an exclusive MoneyGram retail network where payout runs through partner institutions); Home delivery: delivery address and estimated delivery timeframe; Bank / account deposit: receiving institution and account details, masked; Digital wallet: receiving wallet identification, masked.	All categories where the service type is reflected on the receipt. Required.
C10	Local law verification — own-licence and white-label partners: Partners operating under their own licence and white-label partners remain solely responsible for ensuring that their receipts comply with the laws and regulatory requirements applicable in each market where they operate. MoneyGram's review of partner receipts is advisory in nature — it supports consistency with MoneyGram's global standards but does not constitute, and must not be relied upon as, confirmation of compliance with local law. Verify the local legal and regulatory compliance of your receipts on each occasion — at onboarding, whenever your receipt content or transaction flow changes, and whenever local requirements change — obtaining your own legal advice where appropriate.	Own-licence and white-label/MPS models, all receipt categories. Required — standing obligation. The partner's verification of local law compliance is not replaced by MoneyGram's review, by certification, or by the use of content published on this Portal. For the allocation of regulatory responsibility by operating model, see C1–C4.