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
- f4d34e164afc66ec511b9c6b8a5e6fe19f354aaf9f9609da498a76097166948c
- request
- 692db9605833d22f924e0feed2c4645924f0fc6d94bbe7fd36b2619f97e595b0
- transaction
- a9aebb174f68f1cd28a690cba12abb19333afd2a5dcf7161d488026f0a5b52efcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74796
the chainentry 74796
- sealed to the entry before
- aa9cae8e4f3029f9bf7cc20227df8cf9c7457bdbe33c712d6f3163ae9cf01fbd
- this leaf
- a5a5b1c1eba4628d0e42aaf7767ee4e1111d95ffd4cd3e1defe585a822619939
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XGA0I4syJeOJb2A0D8HH3gueEnL/Y4jrqlVkktA2bkmSqyA/NBbJDugNiW5F0hCoWdI3PS7POS3OHS8nWAg2Dw==