Wait for the paid signal.
Use the order and its financial state as the commerce evidence. Shopify documents the orders/paid webhook topic and the fields available on the Order object.
Verify Shopify purchase in Discord
Verify a Shopify purchase and link the buyer to Discord.
A paid order can prove eligibility, but it does not contain a Discord user ID. MemberPort closes that identity gap with a customer claim link, Discord OAuth, bot readiness checks, and a mapped role grant.
Last verified: July 9, 2026
The identity gap
A purchase event is proof of payment, not proof of a Discord identity.
Shopify knows the order, customer, line items, and financial state. Discord knows the member account and server roles. Neither platform can safely infer the missing identity on its own, so the buyer must deliberately connect the two.
Ask the buyer to connect Discord.
A claim link starts an intentional account connection. Discord's OAuth2 flow returns the identity the buyer authorizes instead of guessing from a display name or email.
Check the bot before granting.
The bot must be in the correct server and able to manage the target role. Discord's permissions documentation explains role hierarchy and the Manage Roles permission.
Buyer-to-member flow
Five checks connect a Shopify customer to Discord.
Keep commerce eligibility, account consent, and Discord permissions separate. That makes failed claims diagnosable instead of leaving a merchant with one opaque automation.
01
Shopify buyer qualifies
A paid order contains a product mapped to an access rule. The Shopify customer record is the commerce-side subject of the claim.
02
Claim link reaches the buyer
The buyer opens a claim link tied to that customer and eligibility record. Do not use a public, reusable link that could separate access from the actual buyer.
03
Discord OAuth identifies the member
The buyer authorizes the Discord account they want to use. This supplies the stable Discord identity that the Shopify purchase does not include.
04
Bot readiness passes
MemberPort checks the connected server, detected roles, and whether the hosted bot can manage the mapped role under Discord's hierarchy.
05
Mapped role is granted
The verified Discord member receives the role mapped to the qualifying product, tag, or spend rule, and the access state can be tracked.
Real product screens
Configure the server, then show the member the result.
The setup screen exposes role readiness to the merchant. The Discord confirmation shows the customer that their access is active after a successful claim.
Connected Discord server and detected roles
Active access and granted role confirmation
Troubleshooting checklist
If the Shopify buyer cannot claim a Discord role, check these in order.
Start with the commerce signal, then the claim identity, then Discord permissions. That sequence isolates the layer that failed.
Expected claim state
ORDERPaid + eligible item
CLAIMCorrect Shopify customer
OAUTHIntended Discord account
BOTServer + role ready
RESULTMapped role active
If one state is missing, fix that layer before retrying the claim.
Current lifecycle boundary
Be precise about what is automated today.
MemberPort's current public launch focus is qualification, claim links, pending grants, bot readiness, role granting, and access status. This guide does not promise a full subscription-entitlement engine.
Qualify, claim, and grant.
Use a purchase, customer tag, or spend threshold to qualify the buyer, connect Discord through a claim, and grant the mapped role.
Automatic removal for every lifecycle event.
Refunds, cancellations, subscription expiry, chargebacks, transfers, and automatic role cleanup are not promised by this page.
Test the events your business depends on.
Document the desired result for repeat orders, refunds, renewals, and overlapping products before inviting paying members.
Answers
Shopify purchase verification and Discord claim questions.
Practical answers for merchants connecting Shopify orders to Discord member access.
Can a Shopify order identify a Discord user automatically?
No. A Shopify order identifies the commerce customer, but it does not include a verified Discord user ID. The buyer must connect the intended Discord account through an authorization step such as the MemberPort claim flow.
Should access be granted when an order is created or when it is paid?
For purchase-gated access, use the financial event that matches your policy. MemberPort's purchase-verification flow is described around a paid order so an unpaid, pending, or merely created order is not treated as completed payment.
Does a customer need to create a new Discord account?
No. An existing Discord member can authorize the account they already use. The important checks are that the intended account completes OAuth and is present in the connected Discord server.
What happens if the customer buys the same product twice?
The repeat order can still support eligibility, but the same Discord role should not be duplicated. Keep purchase history separate from the member's current access state and test repeat-order behavior during pilot setup.
Why did the purchase verify but the Discord role fail?
The commerce check and role grant are separate stages. Confirm the buyer authorized the intended Discord account, joined the correct server, and that the MemberPort bot has permission and hierarchy above the mapped role.
Does MemberPort remove a role after a refund or cancellation?
Automatic role removal across refunds, cancellations, subscription expiry, and every other lifecycle event is not promised on this page. The current launch focus is qualification, claims, readiness, role grants, and access status.
Private pilot
Verify the buyer before you open the Discord door.
Join the MemberPort pilot waitlist for hands-on setup around Shopify purchase rules, customer claims, Discord OAuth, bot readiness, and mapped role grants.