Repository navigation
Add X Pay Base facilitator - #150
Merged
Merged
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
2 participants
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.
Summary
Add X Pay (Base) to facilitators.json using the existing registry format. This is X Pay LLC at x-pay.llc, distinct from the existing facilitator.xpay.sh entry.
Facilitator details
Validation
The public /supported endpoint was checked on 9 October 2026 and advertises the Base USDC capabilities above. The following settlement receipt was independently checked on Base: status successful, transaction sender 0x589a2314a2e05f45e40c4823da3ba58d421db3d8, destination Base USDC.
https://basescan.org/tx/0xc39d61e8b9448a3f3a12df5201b6b22b8ce10d0919ceafb7724e75a20bb22ef2
Related pending directory applications with further details:
This change adds one entry only; existing facilitators remain unchanged.
Integration update — 9 October 2026
Capabilities remain public. POST /verify and POST /settle require a merchant API key through X-API-Key or Authorization: Bearer. Unauthenticated empty requests were checked and return HTTP 401. Integration guide: https://facilitator-xpay.llc/docs
The proposed listing has been corrected to match these requirements. No new paid transaction was executed; an authenticated end-to-end settlement test is still pending.