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
- 41a33f15b171f274d9b8d158f6216a471e68d3de557812efcbc18d172d39ecc6
- request
- ddd28637b072fa80bb68154cf19821a2de642d13a0d8a78a0bba92fed0dfb748
- transaction
- a20a90e4d48bba1964413b36c5164d82e6b8fe48ed610c10d15ecf6188dccf22computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65463
the chainentry 65463
- sealed to the entry before
- 70d9b1d98b54a94608186b02b3747729eff9988abfb88fe928c7cdb984e69b3c
- this leaf
- f0cc113730ae1949f503d180cfa08408dd4c72be39370dbf55bbf53dffbd7b78
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AXkmdLrHX2hH0Zo3gFQfR7YA8zt2My0Re/9sXnDN4cWm0V1oKDmt2gdLU8QNtskrcNz7et+clb+TAsh3pFydBg==