mirror of
https://github.com/btcpayserver/btcpayserver.git
synced 2024-11-19 09:54:30 +01:00
e239390ebf
closes #4830 If users want to deal with expired payout destinations, then they should be able to conifugre it that way. Some wallets simply do not allow customizing the bolt11 expiry and the defaults are much less than a day. I think we should merge #3857 if we introduce this as an automated payotu processor for lightning running every few minutes would work together with this and solve it.
33 lines
1.1 KiB
C#
33 lines
1.1 KiB
C#
using System.ComponentModel.DataAnnotations;
|
|
using BTCPayServer.Client.Models;
|
|
|
|
namespace BTCPayServer.Models.StoreViewModels
|
|
{
|
|
public class PaymentViewModel
|
|
{
|
|
public string Id { get; set; }
|
|
|
|
[Display(Name = "Allow anyone to create invoice")]
|
|
public bool AnyoneCanCreateInvoice { get; set; }
|
|
|
|
[Display(Name = "Invoice expires if the full amount has not been paid after …")]
|
|
[Range(1, 60 * 24 * 24)]
|
|
public int InvoiceExpiration { get; set; }
|
|
|
|
[Display(Name = "Add additional fee (network fee) to invoice …")]
|
|
public NetworkFeeMode NetworkFeeMode { get; set; }
|
|
|
|
[Display(Name = "Consider the invoice paid even if the paid amount is ... % less than expected")]
|
|
[Range(0, 100)]
|
|
public double PaymentTolerance { get; set; }
|
|
|
|
[Display(Name = "Default currency")]
|
|
[MaxLength(10)]
|
|
public string DefaultCurrency { get; set; }
|
|
|
|
[Display(Name = "Minimum acceptable expiration time for BOLT11 for refunds")]
|
|
[Range(0, 365 * 10)]
|
|
public long BOLT11Expiration { get; set; }
|
|
}
|
|
}
|