Enable payees (e.g., Storacha SPs) to settle

[timfong888]

Done Criteria

A payee (i.e., someone receiving payment like an Storacha SP) can go to https://pay.filecoin.cloud/console, sign in with their wallet, and hit a button which will effectively callSettle for the amount displayed available to be settled for services rendered.

Why Important

1. Some software like Storacha SP software doesn't automatically settle. They're relying on this mechanism for settling.
2. Generally, service providers should have a way to settle their funds independent of automatic settling.

User/Customer

The most pressing user is Storacha SPs since their software doesn't automatically settle like curio pdpv0.

Notes

1. The current console has a way to do this, but only for payers. We need to open it up for payee.

[timfong888]

When someone calls settleRail(railId, untilEpoch), the contract internally looks up the validator and calls validatePayment() on it if one is configured. Meaning, the explorer never needs to know about any service contract specifically, since it just talks to the Payments contract, which handles the validator lookup on-chain.
The settlement flow is actually already implemented in the explorer (SettleRailDialog). But the catch is that it's currently gated to payers only.
So I think the work here is roughly:
expose this same UI to payees. The subgraph already fetches rails where the connected wallet is either payer OR payee, so the data layer is ready.
loosening that UI restriction and making the "settle" action accessible to SPs (payees).
All this to confirm that anyone with a rail in the payments contract, regardless of their other contracts, should be able to settle their balances. (edited)
4:02
and fwiw, withdrawal would be our next ask, and that's already setup in the UI, and should "just work" in a similar fashion as I've described above.
4:03
Whenever #76 lands I think we'll be good to go without further action/change required on your part.

[BigLep]

The settlement flow is actually already implemented in the explorer (SettleRailDialog). But the catch is that it's currently gated to payers only.

@silent-cipher (I'm @mentioning you because I see you as the person who committed to https://github.com/FilOzone/filecoin-pay-explorer/commits/main/apps/explorer/src/app/console/page.tsx ): do you know why the UI was gated to payers only?

[BigLep]

General question for implementers (e.g., @silent-cipher , @SgtPooki , @pyropy ): I don't see tests around the "explorer" portion of the codebase. What would be a realistic way to start with this change without going overboard?

I can also break the testing question out into its own issue (or feel free to yourselves), but I'm also thinking this new addition is a good forcing function to start moving towards having some tests around this work...

[silent-cipher]

But the catch is that it's currently gated to payers only.

It’s not gated to payers - it’s currently hidden for everyone.
The reason it was hidden is that there used to be a limit on how many epochs could be settled in a single call (≈5 days; when I tested personally, it worked for ~3 days). This was due to the function running out of gas.

More context here: https://filecoinproject.slack.com/archives/C08TVNKJV7C/p1760579212539419

[pyropy]

Per the GA scope defined in XFN-221 this may be out of scope. I'll move this to M4.5

[BigLep]

Per the GA scope defined in XFN-221 this may be out of scope. I'll move this to M4.5

@pyropy : was this explicitly talked about? https://linear.app/filoz/issue/XFN-221/filecoin-pay-ga-scope says existing pages should remain. A big gap on the current "console" is that a user can't settle, and this is about exposing the ability to settle, which we can do now given contract updates (per https://filecoinproject.slack.com/archives/C08TVNKJV7C/p1760579212539419).