why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 65f42d9f21412fbade195f9c5c73404780869f11731b22e658d202b776cf733f
- request
- 5a9e1d16602ef1cda4d99d81b943c99ddc8411400ed18f60503c07fa1de1378a
- transaction
- 4d63acd421e0d22bd99482ea2769ab0f2757cb747911343dde1b38344f23e42fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25248
the chainentry 25248
- sealed to the entry before
- d90ed0cf89c82e435136fe53cf335ecf130ed47e7405a3ce9d02fa431b4cbdab
- this leaf
- 9e4d2b90fb1ffa482734117d677ca08dbbbd95fe0773c6f0e3b69e611c951590
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Y66jbQyZyhiDoO3b73QzIAC+7K6ETZEoJYYnHDIE09NndRrJm2CLKNZkgSHSPTGcBDG9fqroTWhzBhoGwYJbDA==