Ah, that explains it
Payer_data tells the handler what payload should be expected along with the invoice request and if the shape doesn't match it's rejected
payer_data is arbitrary json that can be used for product info, sku's, an email address, anything you want to pipe back out to another system upon payment (works with the webhook callback)
Login to reply
Replies (2)
Oh, that’s interesting. So this is built for a retail payments environment use case, much bigger than just pasting invoices. What point of sale implementations are you targeting, anything production-ready yet?
Maybe just add some explainers to the interface so that people don't add these in the wallet offer UI directly.