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
- 5db0dfff01d3e462204a57533f87cfcb79bb7513c8da65dc1b4692f0dac018ab
- request
- 176a37cb4fe7ff7d975d922e6c8834670d5b1892caaf2a2b0f282860088709c9
- transaction
- f8495d708fcf0b0d6da3165ca10a4bf41981952cc518fccf3f61fb6a3ee9229ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69570
the chainentry 69570
- sealed to the entry before
- 0b4583937b33c3f9774830d984ada68feb4c723de57bce2a5b0b1196dc6848e8
- this leaf
- 74e2c006bfe40599cde4c92bc16a62767d09c04bb5131429441fd86f4fab5b2e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6wBdJ8LGRn3bfALyuQWkECmXVrSC65fYTZHs2YjGWTMI3iAlhCH6byx/ovaJz0TyUH3f525V0YXK6gcvI/fbCQ==