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
- 1ba0b2bc9717543159113ccbead5e7fae1b612065f36fd928ae62079515be846
- request
- d7edbffc92dcffefb90ce54286080d46027a21a93820979481ab2830053432b6
- transaction
- 5b472722030ece4af6f7ae5c325b00304bdc07c04a78ed25e6684fe06bc522b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52359
the chainentry 52359
- sealed to the entry before
- 9766d00c8ae6e31a3c2adafe8a48a5937ba3d972136a90f48eac7b15ea9caa98
- this leaf
- 95441df8b8a668026ea2db8b54e45a012c13215b722aa60a7497575a38d78d4d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N2ZEJBDWIgaUjUKUV94gXStOF2ELL2FYzAgF2thn+nKzgbCyfZVU+pBi4kOOz9hlCywtuAOs/Ega/lZEipmrDQ==