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
- 5b6eb44c9dc87280e11387794a5c95d87cf5243f719ad3b1a93b27b1a78c4457
- request
- 50f5b9137d178aee134d0d319f1887478d46aef5852078586c6706cf42734047
- transaction
- 4908dfb13a7fe3de56f83857fd8c54108320a3ceeb0399c96072eee06b3aea36computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61032
the chainentry 61032
- sealed to the entry before
- 1f3e779c0107c8aa53458d96c3aed8bd20484a6535ff2005da97ea8a8f77748b
- this leaf
- dd6e545f4f8575798518f56d017026dfaba270b04b38a3907d2bae436cb52fea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GzciYwQ9bzfZ8lt3jswkbQ3AdYUK1O15MporTQusTu9kr/yS4/9M9JmcVIg6guJbGbHa455E2ZRJzo4DeccnAw==