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
- 2d6a1ff27fb16e9a3ae305eff30c153f43335cd277baa4131793ca4d91286f4f
- request
- 4d04b78961cabb3d22ae06ebcad22e69c0d7ce640ec21c3b7ebc1285084c3d20
- transaction
- f1ba098a2dbb629b8a578cc828100dec733e4bccb0d4f15a2c9a2d15b679bef0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7086
the chainentry 7086
- sealed to the entry before
- 990ddc10d715f6ae5543d7108cfd6572d3322acf3c8df41d9db1fcd105a6a672
- this leaf
- 6ccb9bfd59333fc71e34606ffb095b345e0bac83732b83485fb7f538b805a987
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4bxKDu74aLkdmw85Rcm4zY5vpnxYbGWsLFKM+O/vme5BieByTCj12sxr1tyBZ4xbnYMoLEBkCbeHvEr+3lpxDg==