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
- daa797d7c183d8b04b0b191efa2fea676a7ae3073ba844f1281bc2566ff10e22
- request
- 10c4c551218b32e2d03d86d0cce1a4044511de922336a3e4049adcc4d7a8af3f
- transaction
- 6a8d3c8056e0793e169ed3d804431b835002736506b3c5bd1508ef2b3fb8593acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1500
the chainentry 1500
- sealed to the entry before
- 5c27a14f36f513d0195c6e9301f6eea487a0d1f11941e9c745dc7eb82bb30cba
- this leaf
- 7af48b39d0b63c3231dbbc8e260e767f2c8495ff246df398c04020b47b0842ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c4HBnwoa4Su4qCavv0OzR2SjgXr3B3a2axkOAUDJSoWZ77NW3GNV2DNCl54liVkh5YhgkjKD6n57P4IXsfRGBA==