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
- 4f63e2756e320f04bd0984a84979e969a88e119e6e92453643393a023667defc
- request
- f83110fe8d666a612b44d53a6160e1a32faa45a170a1fcc7e93a83b9c992b880
- transaction
- e90a1bc5999d6a4204997e9c6ea53b29337809df0caeb3ef9198041eba7e237acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22067
the chainentry 22067
- sealed to the entry before
- e40e2ee3dd857788ce81ed2a4147bdc6833413fa1dbff16a3cd16a0ee766fdcb
- this leaf
- dac4a02d0980787afff0a18870b6004382d8c3d894e56b330c4f56ef72edaba7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 12Bc0GgEcl4QtlC5hvd+4DcbeVWvePWV7BHJaJirkpZiMjlmKs0KhMFHjZXm8cEGLD+Ds6zM1KtTEr3G2+RJDg==