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
- 36cbe4e8f60c8b5994c50b6ea4f6f745525e1389a780a53ca20efd1673598462
- request
- 038174d111d4374c246e44211af4b606ae63318429ad50bb705129ed42fcfc9a
- transaction
- 84574358301afcafdeb71449dde77ef5f51db4805f12c7f8ed5c6a4356727101computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15769
the chainentry 15769
- sealed to the entry before
- 0e4ee1416c3e857ca42b6e7dca5c03cc3952038149bec01edbea3c544047ab6d
- this leaf
- de7df165d0c4bc2c3482f639aa17303a8dea6b3c8a5ceaf3049048820bc566ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pOvQka9DQkgZbHgHUkYrSL20TZwXy7xYniNv/zzWCA77Lr6nYlu93IzSjEY9v/QiJ8pBf4vDD4d7IKD5v/eTDw==