{"id":23426,"date":"2026-01-24T14:22:22","date_gmt":"2026-01-24T13:22:22","guid":{"rendered":"https:\/\/coincharge.io\/bitcoin-payment-privacy-why-bitcoin-lightning-is-superior-to-traditional-payment-methods\/"},"modified":"2026-01-24T14:24:00","modified_gmt":"2026-01-24T13:24:00","slug":"bitcoin-payment-privacy","status":"publish","type":"post","link":"https:\/\/coincharge.io\/en\/bitcoin-payment-privacy\/","title":{"rendered":"Bitcoin payment privacy: Why Bitcoin Lightning is superior to traditional payment methods"},"content":{"rendered":"
[vc_row][vc_column][vc_column_text css=”.vc_custom_1768396325129{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

Paying without a data trail: why Bitcoin Lightning is superior to traditional payment methods<\/span><\/strong><\/h1>\n

<\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]\n

Privacy when paying is no longer a matter of course today<\/h3>\n

People who pay online today rarely pay with money alone.
They pay with data. Lots of data.<\/p>\n[\/vc_column_text][vc_row_inner][vc_column_inner width=”1\/2″][vc_column_text css=””]Name, address, IP address, payment amount, purchasing behavior, location, device information – all of this has long been standard with bank transfers, credit cards or PayPal. Privacy when paying<\/strong> is not intended, but rather a disruptive factor.[\/vc_column_text][\/vc_column_inner][vc_column_inner width=”1\/2″][vc_single_image image=”23381″ img_size=”full” alignment=”center”][\/vc_column_inner][\/vc_row_inner][vc_column_text css=””]\n

This is exactly where Bitcoin comes in.
And the difference becomes even clearer when making a Bitcoin payment via the Lightning network<\/strong>. Because Bitcoin payment privacy<\/strong> is not a marketing promise, but a direct consequence of the technical architecture.<\/p>\n

In this article, we take a look at
which data is generated by traditional payment methods, why this data is passed on – and why Bitcoin Lightning offers significantly greater privacy for payers and merchants.<\/p>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768814492005{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

YouTube: The Transparent Payer: Why your bank knows everything (and Bitcoin doesn’t)<\/strong><\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]We have published a video on the Coincharge YouTube channel<\/a> entitled“The transparent payer: Why your bank knows everything (and Bitcoin doesn’t)<\/a>“[\/vc_column_text][vc_video link=”https:\/\/youtu.be\/PtbLCeE2EjE” align=”center” css=””][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768394341577{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

Today, paying means delivering data<\/strong><\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column width=”1\/2″][vc_column_text css=””]\n

Many people are surprised when they hear that Bitcoin is being talked about in regulatory terms. The real surprise, however, should be how transparent traditional payments have always been<\/strong>.<\/p>\n

When paying by bank, credit card or PayPal, all payment information is passed on along the entire chain:
\nfrom the payer’s bank to payment service providers, card organizations, risk systems and the merchant.<\/p>\n[\/vc_column_text][\/vc_column][vc_column width=”1\/2″][vc_single_image image=”23377″ img_size=”full” alignment=”center”][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]This transparency is intended by law. Officially to combat money laundering and terrorist financing. Critics would add: at least as effective for comprehensive financial monitoring.<\/p>\n

With regulations such as DAC8<\/a>, Travel Rule<\/a> and MiCAR<\/strong>, this model is now also being applied to crypto and Bitcoin payments.
The difference: In the traditional system, this data collection has always been a reality – it has rarely been questioned.[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768394381498{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

A credit card payment is not the push of a button – it’s an interrogation<\/strong><\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_row_inner][vc_column_inner width=”1\/2″][vc_column_text css=””]\n

A nice example was recently provided by an X-Post from “Der Helper”:<\/p>\n

He wanted to buy a powerbank from Germany with a German credit card – delivery to New Zealand.
The payment? Rejected.<\/p>\n

Why?
Because all the alarm bells were ringing in the background.<\/p>\n

This is because a credit card payment is not a direct exchange between the payer and the merchant.<\/p>\n

It is a complex risk process<\/strong> with many parties involved:
card issuer, acquirer, payment network, fraud detection systems, PayPal or other intermediaries if necessary.<\/p>\n

Among other things, the following are tested:<\/p>\n[\/vc_column_text][vc_column_text css=”.vc_custom_1768394423479{margin-left: 50px !important;}”]\n

    \n
  • \n

    Where is the buyer located (IP address)?<\/p>\n<\/li>\n

  • \n

    In which country was the card issued?<\/p>\n<\/li>\n

  • \n

    Who is the cardholder?<\/p>\n<\/li>\n

  • \n

    Which goods are purchased?<\/p>\n<\/li>\n

  • \n

    Which category does the retailer fall into?<\/p>\n<\/li>\n

  • \n

    Where is the delivery made to – and does this match the identity of the payer?<\/p>\n<\/li>\n<\/ul>\n[\/vc_column_text][\/vc_column_inner][vc_column_inner width=”1\/2″][\/vc_column_inner][\/vc_row_inner][vc_row_inner][vc_column_inner width=”1\/2″][vc_column_text css=””]\n

    What happened?<\/p>\n

    In the background, all alarm bells were ringing at the credit card company and the service providers involved. Not because a power bank is dangerous. But because the pattern “Germany \u2192 German credit card \u2192 delivery to New Zealand” occurs in many fraud scenarios.<\/p>\n

    And this brings us to an important point:
    Credit card and PayPal payments are not direct payments between payer and merchant.<\/strong>
    It is a controlled payment with a built-in rewind function – and that needs monitoring.<\/p>\n

    Shipping to the other end of the world?
    From the point of view of fraud systems: highly suspicious<\/strong>.<\/p>\n[\/vc_column_text][\/vc_column_inner][vc_column_inner width=”1\/2″][vc_single_image image=”23387″ img_size=”full” alignment=”center” css=””][\/vc_column_inner][\/vc_row_inner][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768394461287{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

    The real reason for this data collection: chargebacks<\/strong><\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]\n

    Numerous credit card and PayPal checks run in the background to prevent fraudulent payments. After all, if a card is stolen or a PayPal account is hacked, the perpetrator can use the data to make purchases and have the goods delivered.<\/p>\n

    As soon as the actual cardholder realizes that something is wrong, they call their credit card company or report the case to PayPal – and the payment is reversed: Chargeback.<\/p>\n[\/vc_column_text][vc_row_inner][vc_column_inner width=”1\/2″][vc_column_text css=””]\n

    This only works because there is always an intermediary between the payer and the recipient. A middleman. An entity that not only “passes through”, but can also influence payments at any time<\/strong>.<\/p>\n

    This is convenient for consumers. For retailers, it is constant stress.<\/p>\n

    Because a chargeback is not just “theft protection”. In practice, it is also a kind of “joker”:
    One call, one click, one “I wasn’t” – and the retailer no longer has the amount in their account, even though the goods may already be out.<\/p>\n[\/vc_column_text][\/vc_column_inner][vc_column_inner width=”1\/2″][vc_single_image image=”23379″ img_size=”full” alignment=”center” css=””][\/vc_column_inner][\/vc_row_inner][vc_column_text css=””]\n

    And now comes the part that is rarely said so clearly:
    For this system to work at all, it has to collect massive amounts of data and recognize patterns.<\/strong>
    No fraud detection without data. Without fraud detection, chargebacks explode. Without chargebacks, no credit card model.<\/p>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768397959513{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

    You don’t just pay – you are described<\/strong><\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]\n

    Back to the New Zealand powerbank. What was tested?<\/p>\n

    More than you might think. For example:<\/p>\n[\/vc_column_text][vc_column_text css=”.vc_custom_1768397996929{margin-left: 50px !important;}”]\n

      \n
    • \n

      From where was the store visited (IP, Geo)<\/p>\n<\/li>\n

    • \n

      which country and which bank issued the card (issuer)<\/p>\n<\/li>\n

    • \n

      who is the cardholder<\/p>\n<\/li>\n

    • \n

      Which merchant is used for purchases (Merchant)<\/p>\n<\/li>\n

    • \n

      which merchant category (Merchant Category Code)<\/p>\n<\/li>\n

    • \n

      Delivery address vs. cardholder address<\/p>\n<\/li>\n

    • \n

      Purchase history \/ deviations in behavior<\/p>\n<\/li>\n<\/ul>\n[\/vc_column_text][vc_column_text css=””]\n

      All this information not only goes into a “check”, but is also stored, correlated and often passed on to several participants in the chain. This is not a conspiracy – it is simply the technical reality of the traditional payment infrastructure.<\/p>\n

      And this is where it gets exciting, because this is exactly where the contrast to Bitcoin lies.<\/p>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768398055123{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

      Banks are transparent – but not “just a little”<\/strong><\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]\n

      It’s similar with bank payments. Many people believe that a bank transfer is “private” because not everyone can see it. True – but in the banking system, private does not mean “data-poor”, but “centrally collected”.<\/p>\n

      In the case of a bank transfer, your bank knows:<\/p>\n[\/vc_column_text][vc_column_text css=”.vc_custom_1768394561469{margin-left: 50px !important;}”]\n

        \n
      • \n

        your identity<\/p>\n<\/li>\n

      • \n

        Your address<\/p>\n<\/li>\n

      • \n

        your account<\/p>\n<\/li>\n

      • \n

        the payee<\/p>\n<\/li>\n

      • \n

        the intended use<\/p>\n<\/li>\n

      • \n

        the amount<\/p>\n<\/li>\n<\/ul>\n[\/vc_column_text][vc_column_text css=””]\n

        And this information is passed on: at least to the recipient bank – and if necessary to the authorities.<\/p>\n

        Why is KYC-Light enough?<\/h3>\n

        If you buy Bitcoin from a Swiss provider, a KYC-light<\/strong> is sufficient:
        Because if you pay by bank transfer, your own bank has already carried out this identity check.<\/strong>
        The necessary information is already available and is transmitted during the payment process anyway.<\/p>\n

        This is why Swiss lawmakers allow KYC-Light, as the relevant data is already available via the bank.<\/p>\n

        While the Swiss legislator prohibits double data collection, European Bitcoin providers are required to collect additional data:<\/p>\n[\/vc_column_text][vc_column_text css=”.vc_custom_1768395476924{margin-left: 50px !important;}”]\n

          \n
        • \n

          complete identification of the buyer<\/p>\n<\/li>\n

        • \n

          renewed data storage<\/p>\n<\/li>\n

        • \n

          Forwarding of data to other Crypto Asset Service Providers (CASP)<\/p>\n<\/li>\n<\/ul>\n[\/vc_column_text][vc_column_text css=””]Data protection?
          More like a honeypot for hackers<\/strong>.[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768398388335{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

          A classic payment is not final<\/strong><\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]\n

          Payment by bank, credit card or PayPal is never final<\/strong>, but is always subject to change.<\/p>\n

          At first glance, this seems like an advantage for the payer. In reality, this advantage comes at the price of a whole list of side effects:<\/p>\n[\/vc_column_text][vc_column_text css=”.vc_custom_1768398482955{margin-left: 50px !important;}”]\n

            \n
          • \n

            Intermediaries that can block your payment<\/p>\n<\/li>\n

          • \n

            Risk and behavior profiles<\/p>\n<\/li>\n

          • \n

            KYC and identity data in several places<\/p>\n<\/li>\n

          • \n

            Chargeback risk for merchants<\/p>\n<\/li>\n

          • \n

            politically\/corporate motivated blacklists<\/p>\n<\/li>\n<\/ul>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768397201307{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

            Bitcoin payment privacy: final, direct and without intermediaries<\/strong><\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]\n

            With a Bitcoin payment, there is no payment service provider that can intervene.
            No hotline. No chargeback form. No central control authority.<\/p>\n

            As soon as a Lightning payment<\/strong> is completed, it is final<\/strong>.<\/p>\n

            A refund is only possible if the retailer and customer agree to it voluntarily.
            This requires responsibility – on both sides.<\/p>\n

            This is precisely where the crucial difference lies:
            Bitcoin payment privacy is created by eliminating the middleman.<\/strong><\/p>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768398720833{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

            Acceptance contracts: The invisible censorship of payment providers<\/strong><\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]Reversals are the biggest concern of credit card providers and PayPal. That’s why merchants are checked as soon as they are accepted:[\/vc_column_text][vc_column_text css=”.vc_custom_1768398761205{margin-left: 50px !important;}”]\n
              \n
            • \n

              Companies and beneficial owners go through KYC processes<\/p>\n<\/li>\n

            • \n

              Products and business model are evaluated<\/p>\n<\/li>\n

            • \n

              some categories are considered “high risk” and receive higher fees or are rejected<\/p>\n<\/li>\n<\/ul>\n[\/vc_column_text][vc_row_inner][vc_column_inner width=”1\/2″][vc_column_text css=””]\n

              Payment providers are not neutral.
              They are companies – mostly American – and are subject to political guidelines.<\/p>\n

              A real-life example:
              \nA Swiss coffee roaster sells Cuban coffee – exclusively within Switzerland.
              Despite this, his store is blocked because Cuban products are on US sanctions lists.<\/p>\n

              PayPal and credit card providers enforce these rules worldwide.<\/p>\n

              Bitcoin is not interested in this.
              \nA Bitcoin payment<\/strong> is not interested in country of origin, product category or political specifications.<\/p>\n[\/vc_column_text][\/vc_column_inner][vc_column_inner width=”1\/2″][vc_single_image image=”23385″ img_size=”full” alignment=”center” css=””][\/vc_column_inner][\/vc_row_inner][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768398936523{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

              Order data vs. payment data: This is often confused<\/strong><\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]When ordering online, a distinction must be made between:[\/vc_column_text][vc_column_text css=”.vc_custom_1768398971513{margin-left: 50px !important;}”]\n
                \n
              • \n

                Data you need for the delivery (e.g. address)<\/p>\n<\/li>\n

              • \n

                Data that you actually only<\/em> need for the payment<\/em><\/p>\n<\/li>\n<\/ul>\n[\/vc_column_text][vc_column_text css=””]\n

                Why do even digital purchases need your address?<\/strong><\/h3>\n

                Have you ever noticed that you have to give your full address even for a digital product?<\/p>\n[\/vc_column_text][vc_row_inner][vc_column_inner width=”1\/2″][vc_column_text css=””]\n

                For the merchant, the address is often irrelevant for a download, access or digital subscription.
                But because PayPal and credit card providers<\/strong> require it – for risk assessment.<\/p>\n

                This is not necessary for a Bitcoin payment.
                If a product is provided via download, e-mail or access, the merchant does not<\/strong> need an address, name or date of birth<\/strong>.<\/p>\n

                This separation between order data<\/strong> and payment data<\/strong> is a key advantage of Bitcoin.<\/p>\n[\/vc_column_text][\/vc_column_inner][vc_column_inner width=”1\/2″][vc_single_image image=”23383″ img_size=”full” alignment=”center” css=””][\/vc_column_inner][\/vc_row_inner][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768394790037{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

                Lightning: Privacy by design<\/strong><\/h2>\n

                <\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]\n

                With Bitcoin, the payment is structured differently. It is not designed as a “retrievable” payment with a central arbiter, but as a direct transfer of value.<\/p>\n

                Anyone who transfers their Bitcoin to a self-managed wallet<\/strong> and uses a self-custody Lightning Wallet<\/strong> for payments can then pay without disclosing personal data.<\/p>\n

                If you use a self-managed wallet, much of the data that PayPal & Co. collect simply does not exist.<\/p>\n

                The process is important here:<\/p>\n[\/vc_column_text][vc_column_text css=”.vc_custom_1768399406069{margin-left: 50px !important;}”]\n

                  \n
                1. \n

                  You buy Bitcoin from a broker (yes, data is collected there – due to regulation).<\/p>\n<\/li>\n

                2. \n

                  You transfer the Bitcoin to your self-managed wallet (hardware wallet such as BitBox, Trezor or Ledger – depending on the setup).<\/p>\n<\/li>\n

                3. \n

                  If you want to pay, you transfer an amount to a self-managed Lightning Wallet.<\/p>\n<\/li>\n<\/ol>\n[\/vc_column_text][vc_column_text css=””]\n

                  And the following applies to these transfers:
                  No personal data is sent.<\/strong>
                  Because there is no customer account structure that binds identity to every payment.<\/p>\n

                  If you then pay by Lightning, the retailer can only receive what you have to give him anyway:<\/p>\n[\/vc_column_text][vc_column_text css=”.vc_custom_1768399451418{margin-left: 50px !important;}”]\n

                    \n
                  • \n

                    for shipping: delivery address (logical)<\/p>\n<\/li>\n

                  • \n

                    for digital products: often just an e-mail or sometimes no e-mail at all.<\/p>\n<\/li>\n<\/ul>\n[\/vc_column_text][vc_column_text css=””]And back to the New Zealand delivery:
                    With Bitcoin, a merchant does not have to worry that a chargeback will come weeks later because “the card was stolen”.
                    This reduces the need to squeeze delivery addresses into risk models. A New Zealand address is then not automatically an alarm signal – but simply an address.[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=”.vc_custom_1768395776392{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”]\n

                    Conclusion: Privacy is not a bug – it’s a feature<\/strong><\/h2>\n

                    <\/h2>\n[\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][vc_column_text css=””]Bitcoin Lightning offers something that traditional payment systems have systematically abolished: Privacy through technical separation of payment and identity<\/strong>.<\/p>\n

                    Bitcoin payment<\/strong> means privacy<\/strong>:<\/p>\n[\/vc_column_text][vc_column_text css=”.vc_custom_1768399552395{margin-left: 50px !important;}”]\n

                      \n
                    • \n

                      Clear separation between order data and payment data<\/p>\n<\/li>\n

                    • \n

                      No automatically enforced identity disclosure<\/p>\n<\/li>\n

                    • \n

                      No central authority to reverse payments<\/p>\n<\/li>\n

                    • \n

                      Fewer data hoards – fewer honeypots for hackers<\/p>\n<\/li>\n<\/ul>\n[\/vc_column_text][vc_column_text css=””]\n

                      For merchants, this means: less chargeback risk, less payment censorship, more planning security.
                      For payers, this means: more control over their own data.<\/p>\n

                      Bitcoin Lightning shows that payment can also work differently:
                      minimalist, direct and data-saving<\/strong>.<\/p>\n

                      Just as Satoshi Nakamoto envisaged in the white paper.
                      And this is precisely why Bitcoin is a step forward in digital payment transactions.<\/p>\n[\/vc_column_text][\/vc_column][\/vc_row]\n<\/div>","protected":false},"excerpt":{"rendered":"

                      [vc_row][vc_column][vc_column_text css=”.vc_custom_1768396325129{padding-top: 30px !important;padding-bottom: 30px !important;background-color: #6193C9 !important;}”] Paying without a data trail: why Bitcoin Lightning is superior to traditional […]<\/p>\n","protected":false},"author":1,"featured_media":23353,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[58],"tags":[],"class_list":["post-23426","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-accept-bitcoin"],"_links":{"self":[{"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/posts\/23426","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/comments?post=23426"}],"version-history":[{"count":4,"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/posts\/23426\/revisions"}],"predecessor-version":[{"id":23432,"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/posts\/23426\/revisions\/23432"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/media\/23353"}],"wp:attachment":[{"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/media?parent=23426"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/categories?post=23426"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/coincharge.io\/en\/wp-json\/wp\/v2\/tags?post=23426"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}