Btcpayserver: How to change Contact & Refund Email invoice page

[lrgeoemtry]

I'm in need of changing this copy to say somehting like

"Insert your Ethereum Address for Delivery of tokens"

but i can't find it

All i can find is
"Require a Refund Email"

Also, how to keep the cart up for the user longer after payment? It just goes away with no confirmation of payment.

Any help is awesome.

Thanks

[pavlenex]

You would have to fork BTCPay Server and apply changes, maintain your own fork with the change, it's currently not possible to do it in an easy, non-technical and out of the box way.

[lrgeoemtry]

=/
Well thanks for the answer.

Maybe make this a feature request :
Instead of
Require Refund Email
Which doesnt seem trustless
Make it a free form text field ?

If i could ask for the user's wallet address by Friday that would be
great...

https://images.app.goo.gl/EUCcbLEUyjL3RgJT9

Lmk if possible.

Cheers

On Sat, 25 May 2019, 19:53 Pavle, [e-mail] wrote:

You would have to fork BTCPay Server and apply changes, maintain your own
fork
https://docs.btcpayserver.org/faq-and-common-issues/faq-serversettings#how-to-customize-my-btcpay-theme-style
with the change, it's currently not possible to do it in an easy,
non-technical and out of the box way.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/btcpayserver/btcpayserver/issues/862?email_source=notifications&email_token=AGGBNUBE53XBCBA3SZNGBDDPXHNPJA5CNFSM4HPVR5LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWH3V3Q#issuecomment-495958766,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGGBNUG2BERXKRGZPKK55BTPXHNPJANCNFSM4HPVR5LA
.

[Kukks]

If you did change the text to say that, the system is hard-coded to validate it against an email format. We have an idea on how to extend the system further to be able to add your own forms but it's still a rough idea needing to be properly specced out and developed.

No ETA.

[pavlenex]

In that case, this request is a sort of a duplicate of #671 so I'll proceed with closing it.

We do have an idea to make this more configurable in the future as @Kukks.