INXY Payments primary sources — 2026-05-02

Project status in this pass

• No canonical standalone INXY Payments whitepaper or litepaper surfaced.
• The official site was only partially extractable during this pass because the rendered page content did not come through cleanly via lightweight fetch.
• Even so, first-party site titles plus official GitHub SDK repositories revealed a coherent developer-facing crypto-payments footprint.

Primary-source snapshots

1) Homepage title and positioning

• URL: https://www.inxy.io/
• Key excerpt:
  • The homepage title is “Crypto Payment Gateway for Business — INXY Payments.”
  • Official-site search snippets tied to that page describe INXY as an EU-authorized and Canada-registered platform for accepting, sending, and managing cryptocurrencies.
  • Even without full rendered extraction, that combination strongly frames INXY as a regulated B2B crypto-payments vendor.

2) Fintech page title and positioning

• URL: https://www.inxy.io/fintech
• Key excerpt:
  • The page title is “Fintech Crypto API & Stablecoin Infrastructure | INXY Payments.”
  • Official-site search snippets for the same page say the API lets builders plug stablecoin payments, payouts, and conversions into their product without building their own crypto engine.
  • This is the strongest clue that INXY is targeting fintech backends in addition to merchant checkout.

3) Merchant SDK repository

• URLs:
  • https://github.com/inxy-payments/merchant-sdk
  • https://raw.githubusercontent.com/inxy-payments/merchant-sdk/master/README.md
• Key excerpt:
  • The README shows a PHP/Composer package named inxy-payments/merchant-sdk.
  • Example code creates a MultiCurrencySessionRequest, sets supported cryptocurrencies, assigns customer and redirect URLs, and then redirects the user to a payment page returned by createMultiCurrencySession.
  • Supported examples include USDT on Ethereum and BNB Smart Chain, BTC, ETH, DOGE, and USDC, which suggests a hosted multi-asset checkout product rather than a single-coin gateway.

4) Webhook validation flow in merchant SDK

• URL: https://raw.githubusercontent.com/inxy-payments/merchant-sdk/master/README.md
• Key excerpt:
  • The README documents validating an X-INXY-Payments-Signature header with a shared secret.
  • It handles event names such as PaymentsInit, PaymentsWaitingConfirmations, and PaymentsReceived.
  • Status handling includes WaitingPayment, WaitingPaymentPart, Paid, and PartiallyPaid, showing a fairly operational webhook model around crypto payment settlement.

5) Signature SDK repository

• URLs:
  • https://github.com/inxy-payments/signature-sdk-js
  • https://raw.githubusercontent.com/inxy-payments/signature-sdk-js/master/README.md
• Key excerpt:
  • The signature-sdk-js README says the package creates digital signatures using RSA encryption and PEM encoding.
  • The package returns a Base64 signature and timestamp from a payload string, private key, and current time.
  • This strongly suggests INXY maintains explicit request-signing or auth tooling as part of its broader API strategy.

Working conclusion

INXY Payments is best cataloged as crypto payment gateway and stablecoin API infrastructure for merchants and fintechs. The deciding evidence in this pass was the combination of first-party B2B/stablecoin site positioning and the official SDK footprint for multi-currency checkout, signed webhook handling, and developer signing utilities. A caveat for future passes is that the main website should ideally be revisited with a richer browser-based capture method to validate more of the marketing and regulatory claims directly from rendered first-party page content.