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
- 574554e406245d63ac39839e2d079b593eac192985c592f9ab5452981cbca56d
- request
- a53e31bf730019296b13c22205bb3ebe3cb89a7a9b9cef48ecce12bd38c52ce6
- transaction
- ae81f56ea3e03ab38f5b238467a327f4e632a8e1623bf010a52db2fef9723273computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 546
the chainentry 546
- sealed to the entry before
- d592bcaabac75c0495e6d6f411d6b22dbc91902bdcc9fd43ebdd9d3b1236429d
- this leaf
- 975dfab9a814d3c6aca87441670478e25119ab775fa08b1bedbc3f5d095396e5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3F9rhAr8Zgr3SFqXCJ2SC+n6ZN4PKJo+dnNsW69yTxI8on02zYoxerlXEXrlll/B9Ymi1AAtw9Q4plfgA03gCw==