Put XGuard inside WordPress x402 Pay facilitator selection - #479
Open
moelayyan90 wants to merge 4 commits into
Open
Put XGuard inside WordPress x402 Pay facilitator selection#479moelayyan90 wants to merge 4 commits into
moelayyan90 wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a native external facilitator connector for Automattic
x402-Pay/ WordPress 7.0 Connectors API.The goal is distribution inside an existing payment path: after installing the connector, site owners can select XGuard — Base mainnet directly from Settings → x402 Pay → Facilitator.
Implementation:
x402_facilitatorX402FacilitatorClienthttps://api.xguardgate.comXGUARD_LICENSE_KEYconstant/env adds Bearer authorization for Usage CreditsNo WordPress.org or Automattic approval is claimed by this PR.