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
- e20e1645218fe3d895766beeb8f02f7ec6713a783e3ac08d46e48980eaae6f91
- request
- 17d108d84c8024a564985ddde5e3535b8b08779eaf5508ecd8732c804694e6f0
- transaction
- 79b55ee8322ef8cc07edbcd33be6272db1e4acc2c08a80e648dd301244be0f27computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10962
the chainentry 10962
- sealed to the entry before
- 034ba5f40fbfe1b8615506ef49027a2f1cd7273e3732052a7615d4cb78dabb6c
- this leaf
- 2cee5ec583447981bbc31106b4f076b7815a5e4551dedf67b80a3e2c8a498dfe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EEKbnflqAhKmxMmz/zqDU0G38aU9cHvWkSAZ5UFA1u1HDW3n1ro+dgJ9bJkmEIrQVgjgwaEvno5XOcEpW2lICg==