Add Blockonomics payment gateway (BTC & USDT) to the extension directory

[anktd]

Preflight Checklist

• I have searched existing issues and confirmed this has not already been suggested.
• This is a product or documentation improvement, not a support request.

Request Type

New Feature

Affected Area

Extension, Module, or Integration

Repository or Component

FOSSBilling/extensions

Problem or Use Case

I maintain the Blockonomics payment gateway extension for FOSSBilling and would like it listed in the extension directory, per the submission note in this repo's README.

Repo: https://github.com/anktd/blockonomics-fossbilling

The extension lets FOSSBilling merchants accept Bitcoin (BTC) and Tether (USDT, ERC-20) payments that go directly to their own wallet. Non-custodial, no KYC.

Proposed Solution

List the extension in the directory. Full listing details:

• Name: Blockonomics
• Type: payment-gateway
• Description: Accept Bitcoin (BTC) and Tether (USDT, ERC-20) payments directly to your own wallet.
• Author: Blockonomics (organization)
• Source: https://github.com/anktd/blockonomics-fossbilling
• License: Apache 2.0 - https://github.com/anktd/blockonomics-fossbilling/blob/master/LICENSE
• Release: 0.2.0
• Download: https://github.com/anktd/blockonomics-fossbilling/releases/download/0.2.0/Blockonomics.zip
• Install: extract the zip inside /library/Payment/Adapter/, then install from System → Payment gateways
• Minimum FOSSBilling version: 0.8.3 (PHP 8.2+)
• Icon: https://raw.githubusercontent.com/anktd/blockonomics-fossbilling/master/icon.png
• Website: https://www.blockonomics.co/

Happy to provide anything else needed, or to follow the self-service submission flow once it's available.

Alternatives Considered

No response

Additional Context

Blockonomics is a non-custodial crypto payments provider. I maintain official payment plugins for WooCommerce and WHMCS, and this extension brings the same integration to FOSSBilling. Checkout is fully on-page including on page payment status updates, invoices settle via callback after 2 network confirmation, and a one-click Test Setup verifies the merchant's configuration end to end.

The extension has been tested internally on FOSSBilling 0.8.3 and 0.2.0 is released and ready. Feedback welcome.

[anktd]

Hello @admdly can you please look into this.

[admdly]

The extension directory is currently being updated which is why extensions must be manually added, but I will review this and get the extension added today.

[anktd]

Hi @admdly, just following up. Please let me know if you need anything from my side to get the extension added.

[admdly]

@anktd apologies for the delay due to ongoing changes with the directory - I'll push this manually to the directory by the end of the day if I have no further update by then.

[anktd]

Gentle bump on this when you get a moment, @admdly , no rush, and happy to handle anything needed from my side. Thanks!

[admdly]

Sorry for taking longer than planned with this.

Could you create an account and developer profile on https://extensions.fossbilling.org using the "Developer sign-in" link in the top right, then the "Create" option next to "Developer Profile" once logged in? You should then be able to submit the extension for review using the "Submit New Extension" option.

If you have any issues, let me know and we can get them sorted.

[anktd]

Hi @admdly, thanks! Tried the Developer sign-in but it fails right away with a "Sign-in failed" toast.
Looks like the OAuth client is requesting a github scope that isn't enabled on the auth server (the authorize redirect comes back with error=invalid_scope: The following scopes are invalid: github). I will complete the submission flow once that's sorted!

[admdly]

Hi @admdly, thanks! Tried the Developer sign-in but it fails right away with a "Sign-in failed" toast.
Looks like the OAuth client is requesting a github scope that isn't enabled on the auth server (the authorize redirect comes back with error=invalid_scope: The following scopes are invalid: github). I will complete the submission flow once that's sorted!

Apologies - could you check this again? The auth flow had been updated and a backfill was missed. It should now be sorted.