mirror of
https://github.com/btcpayserver/btcpayserver.git
synced 2025-02-23 06:35:13 +01:00
51690b47a3
* Automated Transfer processors This PR introduces a few things: * Payouts can now be directly nested under a store instead of through a pull payment. * The Wallet Send screen now has an option to "schedule" instead of simply creating a transaction. When you click on schedule, all transaction destinations are converted into approved payouts. Any options relating to fees or coin selection are discarded. * There is a new concept introduced, called "Transfer Processors". Transfer Processors are services for stores that process payouts that are awaiting payment. Each processor specifies which payment methods it can handle. BTCPay Server will have some forms of transfer processors baked in but it has been designed to allow the Plugin System to provide additional processors. * The initial transfer processors provided are "automated processors", for on chain and lightning payment methods. They can be configured to process payouts every X amount of minutes. For on-chain, this means payments are batched into one transaction, resulting in more efficient and cheaper fees for processing. * * fix build * extract * remove magic string stuff * fix error message when scheduling * Paginate migration * add payout count to payment method tab * remove unused var * add protip * optimzie payout migration dramatically * Remove useless double condition * Fix bunch of warnings * Remove warning * Remove warnigns * Rename to Payout processors * fix typo Co-authored-by: Nicolas Dorier <nicolas.dorier@gmail.com>
40 lines
2.2 KiB
C#
40 lines
2.2 KiB
C#
#nullable enable
|
|
using System;
|
|
using System.Collections.Generic;
|
|
using System.Threading.Tasks;
|
|
using BTCPayServer.Abstractions.Models;
|
|
using BTCPayServer.Client.Models;
|
|
using BTCPayServer.Data;
|
|
using BTCPayServer.Payments;
|
|
using Microsoft.AspNetCore.Mvc;
|
|
using PayoutData = BTCPayServer.Data.PayoutData;
|
|
using StoreData = BTCPayServer.Data.StoreData;
|
|
|
|
public interface IPayoutHandler
|
|
{
|
|
public bool CanHandle(PaymentMethodId paymentMethod);
|
|
public Task TrackClaim(PaymentMethodId paymentMethodId, IClaimDestination claimDestination);
|
|
//Allows payout handler to parse payout destinations on its own
|
|
public Task<(IClaimDestination destination, string error)> ParseClaimDestination(PaymentMethodId paymentMethodId, string destination);
|
|
public (bool valid, string? error) ValidateClaimDestination(IClaimDestination claimDestination, PullPaymentBlob? pullPaymentBlob);
|
|
public async Task<(IClaimDestination? destination, string? error)> ParseAndValidateClaimDestination(PaymentMethodId paymentMethodId, string destination, PullPaymentBlob? pullPaymentBlob)
|
|
{
|
|
var res = await ParseClaimDestination(paymentMethodId, destination);
|
|
if (res.destination is null)
|
|
return res;
|
|
var res2 = ValidateClaimDestination(res.destination, pullPaymentBlob);
|
|
if (!res2.valid)
|
|
return (null, res2.error);
|
|
return res;
|
|
}
|
|
public IPayoutProof ParseProof(PayoutData payout);
|
|
//Allows you to subscribe the main pull payment hosted service to events and prepare the handler
|
|
void StartBackgroundCheck(Action<Type[]> subscribe);
|
|
//allows you to process events that the main pull payment hosted service is subscribed to
|
|
Task BackgroundCheck(object o);
|
|
Task<decimal> GetMinimumPayoutAmount(PaymentMethodId paymentMethod, IClaimDestination claimDestination);
|
|
Dictionary<PayoutState, List<(string Action, string Text)>> GetPayoutSpecificActions();
|
|
Task<StatusMessageModel> DoSpecificAction(string action, string[] payoutIds, string storeId);
|
|
Task<IEnumerable<PaymentMethodId>> GetSupportedPaymentMethods(StoreData storeData);
|
|
Task<IActionResult> InitiatePayment(PaymentMethodId paymentMethodId, string[] payoutIds);
|
|
}
|