<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>thread GIFT CARD fees in Orders, Menu Items, Catalog &amp; Fulfilment</title>
    <link>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/GIFT-CARD-fees/m-p/840584#M23196</link>
    <description>&lt;P&gt;We're building a coin redemption integration using the Square Gift Card API. Our flow is entirely programmatic — not a consumer-facing gift card product:&lt;BR /&gt;Consumer initiates a coin redemption at checkout&lt;BR /&gt;Twism calls the Gift Card API to create a gift card and load it with the redemption value via loadGiftCardBalance()&lt;BR /&gt;The gift card is passed to the cashier as a one-time-use tender&lt;BR /&gt;Cashier processes it via "Pay with Gift Card" at the Square POS terminal&lt;BR /&gt;The gift card is never sold to the consumer — it's created and consumed in a single transaction as a payment instrument.&lt;/P&gt;&lt;P&gt;Question&lt;BR /&gt;We found this support article which mentions:&lt;BR /&gt;A 2.5% load fee for gift cards&lt;BR /&gt;A 3.3% + 30¢ processing fee for digital eGift cards&lt;BR /&gt;We want to confirm specifically:&lt;BR /&gt;Does calling loadGiftCardBalance() via the API trigger the 2.5% load fee on the merchant's Square account?&lt;BR /&gt;Does the fee structure for API-created gift cards used as POS tender differ from gift cards sold to consumers (retail or eGift)?&lt;BR /&gt;If a fee applies — is it charged to the merchant's account or to the account associated with the API credentials (in our case, Twism's)?&lt;BR /&gt;We previously received verbal confirmation that there would be no fees associated with this flow, but we want written confirmation before proceeding with merchant rollout.&lt;/P&gt;</description>
    <pubDate>Thu, 09 Apr 2026 21:11:05 GMT</pubDate>
    <dc:creator>twism_developer</dc:creator>
    <dc:date>2026-04-09T21:11:05Z</dc:date>
    <item>
      <title>GIFT CARD fees</title>
      <link>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/GIFT-CARD-fees/m-p/840584#M23196</link>
      <description>&lt;P&gt;We're building a coin redemption integration using the Square Gift Card API. Our flow is entirely programmatic — not a consumer-facing gift card product:&lt;BR /&gt;Consumer initiates a coin redemption at checkout&lt;BR /&gt;Twism calls the Gift Card API to create a gift card and load it with the redemption value via loadGiftCardBalance()&lt;BR /&gt;The gift card is passed to the cashier as a one-time-use tender&lt;BR /&gt;Cashier processes it via "Pay with Gift Card" at the Square POS terminal&lt;BR /&gt;The gift card is never sold to the consumer — it's created and consumed in a single transaction as a payment instrument.&lt;/P&gt;&lt;P&gt;Question&lt;BR /&gt;We found this support article which mentions:&lt;BR /&gt;A 2.5% load fee for gift cards&lt;BR /&gt;A 3.3% + 30¢ processing fee for digital eGift cards&lt;BR /&gt;We want to confirm specifically:&lt;BR /&gt;Does calling loadGiftCardBalance() via the API trigger the 2.5% load fee on the merchant's Square account?&lt;BR /&gt;Does the fee structure for API-created gift cards used as POS tender differ from gift cards sold to consumers (retail or eGift)?&lt;BR /&gt;If a fee applies — is it charged to the merchant's account or to the account associated with the API credentials (in our case, Twism's)?&lt;BR /&gt;We previously received verbal confirmation that there would be no fees associated with this flow, but we want written confirmation before proceeding with merchant rollout.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Apr 2026 21:11:05 GMT</pubDate>
      <guid>https://community.squareup.com/t5/Orders-Menu-Items-Catalog/GIFT-CARD-fees/m-p/840584#M23196</guid>
      <dc:creator>twism_developer</dc:creator>
      <dc:date>2026-04-09T21:11:05Z</dc:date>
    </item>
  </channel>
</rss>

