On this page
A customer who has made several purchases may want one place to find the related rewards. The useful first version is often a list of references and next steps, not a dashboard full of card details. That narrower purpose makes the page easier to understand and gives the integration a smaller disclosure boundary.
Consider a hypothetical cycling store. A signed-in buyer has three purchases: one reward is under review, another has instructions available through an approved provider experience, and a third purchase has no associated reward. The account area should help the buyer distinguish those cases without pretending that Shopify natively stores a complete reward-card history.
Choose a customer-account target and reference schema
Shopify offers customer-account UI extension surfaces with documented targets and authentication capabilities. Select the target and account model supported by the store, then pin the version used for the implementation review. Shopify customer account UI extensions
A full-page reference area and a small account block solve different needs. A compact block might show a recent reward and a link to a larger approved experience. A dedicated area can support pagination and several purchase references. Choose based on the customer task and actual surface support rather than drawing a large interface first and looking for somewhere to place it later.
The proposed schema should contain only what the page needs. For the cycling example:
| Display field | Hypothetical value | Purpose |
|---|---|---|
| Purchase label | Order 2048 | Helps the customer recognize the purchase |
| Opaque reward reference | AW-2048-A | Connects support and provider records |
| Approved stage | Purchase review pending | Explains the current task state |
| Relevant date | Last checked September 12 | Establishes freshness |
| Allowed next action | View approved instructions | Guides the next step |
| Safe destination category | Provider reward experience | Describes where navigation leads |
These are proposed application fields. They are not a published RebateCardX API response. A real integration must use the reviewed provider contract and its supported disclosures.
Exclude card numbers, security codes, live claim tokens and unrelated customer attributes from this reference model. The account extension should not become an accidental card vault because a developer finds it convenient to store every provider response in customer metadata. A reference page can be useful without taking responsibility for displaying sensitive card credentials.
Define the ordering rule. “Most recent” could mean purchase date, award approval date or last status change. For a purchase-linked list, ordering by purchase date may be easiest for customers to understand. Show meaningful stage changes within each row rather than letting frequent background updates constantly reshuffle the list.
Return only records authorized for the signed-in customer
The backend must establish the current store and customer from the supported authenticated context. It should not accept an email address from the browser as the sole instruction to return matching reward records. A client-supplied filter can request a view, but it cannot define the viewer’s authority.
Build the lookup around the approved relationship between customer, purchase and reward. In the fictional store, a buyer may be authorized to view the purchase’s reward stage while a gift recipient owns the separate claim journey. If those identities differ, the response should follow the program’s disclosure policy rather than merge them because they share an order.
Shopify distinguishes access scopes from its protected-customer-data requirements. Availability of a field must be confirmed under both the technical access contract and the applicable data approval process. Shopify protected customer data
Pagination belongs inside the authorization boundary. A next-page cursor should continue the same trusted tenant and viewer scope. It should not allow a customer to replace a hidden identifier and browse someone else’s list. Test the second and final pages as carefully as the first, because access defects often appear in alternate query paths.
A reference list needs at least four empty or partial states. “No purchase-linked rewards found” is appropriate only when the lookup completed within the approved scope. “We cannot retrieve your reward references right now” describes a service problem. “Some older purchases are outside this connection’s available history” describes a known coverage limit. “Return through the supported sign-in route” describes an access problem. One generic empty screen cannot explain all four.
For the example, suppose the integration began after the customer made an earlier purchase. Do not infer that the older order had no reward merely because the current service lacks its history. If historical coverage is limited, state that limit in the page contract and provide the approved route for unresolved older cases.
The backend can also return a completeness indicator for the list, provided the actual adapter supports one. That indicator helps the frontend avoid claiming “all rewards” when it is displaying only the currently connected program. A modest title such as “Reward references for this program” may better match the available data.
Define navigation to the approved reward experience
Each action should describe what the destination actually does. “View reward instructions” is different from “Use your card.” If the linked experience still requires a claim step or identity check, the account page should not imply that navigation immediately reveals a spendable card.
Review destination ownership with the provider. Use only approved hosts and the supported access method. An ordinary account link should not carry raw credentials or expose a bearer secret in a place that will be copied into analytics logs. Where the provider contract uses a sensitive navigation token, handle it through the reviewed flow rather than inventing a permanent URL in customer metadata.
The fictional wireframe can be written as a filled example:
| Purchase | Stage | Next step |
|---|---|---|
| Order 2048 | Review pending | Read the approved timing explanation |
| Order 2011 | Instructions available | Open the authorized provider experience |
| Order 1980 | No reference in this program | Review purchase coverage guidance |
The third row should appear only if the product decision is to show relevant purchases without awards. Another valid design lists only actual reward references and explains the coverage limit above the list. Choose one model deliberately; otherwise the customer may interpret an omitted purchase as a technical failure.
Test navigation with an expired session, a changed customer context, a removed program connection and a provider destination that is temporarily unavailable. The account area should retain a useful reference and truthful guidance rather than dropping the customer into an unexplained error page.
A difficult case is account consolidation. If two customer records are merged or a login identifier changes, do not silently join their reward history using a broad email match. Review how the actual Shopify and provider contracts represent the change, then reestablish the authorized associations. Until that is resolved, a limited list is safer than an unsupported disclosure.
The finished specification consists of a target choice, a minimal reference schema, scoped list behavior and navigation acceptance cases. It gives customers continuity across purchases while leaving the approved card experience with the party and system responsible for it.
One useful acceptance artifact is a filled two-page list. Put an authorized reward on the first page, a second authorized reward on the next page and an unrelated customer’s reference outside the expected result. Confirm that changing the page cursor cannot expose the unrelated reference and that returning to the first page preserves the same coverage explanation. Then remove the provider connection in the test fixture. The account area should describe unavailable history without reclassifying either known reward as rejected or erased.
Request access to discuss a supported customer-account reward experience.
Source references
This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.
