Store

01What members see#

Members browse the Store in your community or through its widget in your client portal.

1. 01Browse categories, search and product cards with prices in coins.
2. 02Open a product. If it offers redemption methods, choose one and fill in its fields, such as a trading account number.
3. 03Confirm the purchase. Coins leave the balance and one voucher code is taken from that product's stock.
4. 04See the confirmation and order in Purchase History. Its starting status follows your product or category settings, otherwise New Purchase. The platform also sends a purchase email.
5. 05Open Order Details for the voucher code and expiry. Your team or integration handles any further fulfilment and updates the status; orders need not pass through every stage.

From the product

Screenshots from a test community with synthetic products and redacted member details. Method names are broker-written labels; the Store does not calculate the credit amount.

Members may also see Coming Soon, Purchase Limit Reached, a spending-cap message, Not Eligible for a method, or a payment failure with Try Again. Disabled purchase buttons explain why they cannot buy.

02What you control#

Configure the Store at three levels: Store settings, categories and products. A product can sit outside a category.

Store settings

Category

Product

03How it works#

Building the catalogue

• Price products in coins from your chosen coin value. At the example $0.005 per coin, a $50 item is 10,000 coins and takes 100 FX lots to earn at 100 coins per lot.
• Discounted prices apply inside their date window. Category or product access can show, hide or restrict purchasing. A product rule overrides its category rule.
• Voucher codes are the stock. Each purchase takes one active, unexpired code; the standard Store flow issues the earliest-expiring valid code first. When no unexpired voucher codes remain, the product is out of stock.
• A purchase must fit applicable Store and category spending caps. A coin price that exceeds the remaining allowance is blocked. These caps limit coins spent, not cash fulfilment or credit exposure.
• Purchase limits use calendar blocks. Weeks start Monday and years reset on 1 January. Within an applicable permission scope, the most generous matching limit applies.

Redemption methods

Methods are labels and data-collection choices you write. A product has one coin price, shared by every method on it. The Store does not grant trading credit or funds from that label.

Use one product with several methods when every choice should cost the same coins. Use separate products for different coin prices, purchase limits or access rules.

1. 01The member selects a method, fills in its fields and passes any eligibility check.
2. 02The Store deducts coins, consumes one voucher code, creates the order and sends a purchase email.
3. 03Your integration maps the chosen method to a reward, grants credit or funds when relevant, then updates the order after fulfilment.

Orders and refunds

• Orders use four stages: New Purchase, In Progress, Completed and Refunded. You can add statuses inside them. A new order uses the product override, then category default, then New Purchase.
• The Store does not confirm external fulfilment automatically. Your team or integration updates the status when it is confirmed.
• You can allow member refund requests, select eligible statuses and choose approval or automatic refund.
• A successful coin refund returns the price paid once per order. A Refunded-category order no longer counts toward the purchase limit. The Store attempts to restore an unexpired voucher and adjusts spending-cap usage for the original purchase period. Check the order, stock and cap after refund.
• Moving an order out of Refunded does not take the coins back. Your integration must reverse any broker-side credit or funds already granted.

04Ways to use it#

Seven example catalogue patterns use the same planning coin value: $0.005 per coin, or 200 coins per $1.

05Planning your economics#

At the example rates, $0.50 of reward value per FX lot makes a $50 item cost 10,000 coins, or 100 FX lots and 100 Metals lots. Monthly issuance is 2,000,000 coins; 60% redemption means 1,200,000 coins spent. The example mix gives $4,500 credit face value and $3,000 cash out before shipping and modelled credit cost.

06Timing and limits#

• Coins are deducted and the order is created at purchase. Shipping, credit or funds follow your fulfilment process.
• Discounts apply only inside their start and end dates. Outside the window, the normal price applies.
• Purchase limits use calendar blocks; spending caps follow their configured timezone and interval. A completed refund adjusts usage in the original purchase period, which may differ from the current period.
• Retry the same purchase with unchanged details to avoid a second charge. A completed retry returns the original order; changed details are rejected.
• Store purchases consume the earliest-expiring available coins first. Refund processing puts coins into the earliest future expiry window. If none exists, the current expiry policy applies or the balance does not expire. A refund does not necessarily restore the original expiry date or grant a fresh full expiry period.
• The voucher code appears in Order Details after purchase and is hidden after a refund. Members can see later status changes in the Store; status changes do not send a member email.

07Not supported yet#

• Not supported

  Cash checkout in the current Store purchase flow

  Members pay the product's coin price.

• Not supported

  More than one unit per order

  Each order is quantity one. Buying twice creates two orders.

• Not supported

  Different coin prices per method on one product

  Use separate products if the methods need different prices or rules.

• Not supported

  Stock without voucher codes

  Every product needs codes as inventory, including trading credit and funds products.

• Not supported

  Automatic trading-account fulfilment

  Connect your own fulfilment system to order notifications or the widget callback, then update the order.

• Not supported

  Automatic broker-side reversal on refund

  Your systems must undo credit or funds already granted.

• Not supported

  Built-in cumulative trading credit cap

  Your integration must enforce any account-level or programme-wide credit exposure limit.

08For your developers#

Share these published pages with the team maintaining your Store integration. Ask your success manager to confirm how your systems receive order notifications and the chosen method fields.

• Get Store configuration→
• Update Store configuration→
• List Store categories→
• Create a Store category→
• Update a Store category→
• List products→
• Create a product with vouchers→
• Update product and append vouchers→
• List redemption orders by community→
• List redemption orders by member email→
• Update redemption order status→
• List redemption statuses→
• Create a redemption status→
• Get redemption transaction detail→
• Update redemption instructions or voucher details→
• Workflow webhooks→