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
- 2e7d9fac97b26e8c9d3d9f0c5f6e69179ef8796a05281be4cde6c8890c91d3b6
- request
- 0a979f06b0dcf1e847ae5c4392f71ce7796226b60ab2b7003f26521e21641627
- transaction
- 8b7ba1f36421164fcd7cb7a1949cb869a33b4ebfaf1f07b02fe7ba60cb198d1acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29343
the chainentry 29343
- sealed to the entry before
- d49c2f566db2a37e37f0ee15edf554281b98f3eedc8ac455bdb1e5a54d78da46
- this leaf
- fa42ce05a60569552ff86c388e22c0375cb0b7f65bf04d868dde7d313028a9fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6p0WWJMB6aCvwpTYB8kXv0+w1qAH3cZo+hY9/G6BRbRth3O3PBQVHA9rNOPK6vekYY3Kj05eDHvHQUCdJ1q4AA==