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
- 5d7eb8f1175e4e548584273e2777a04077f63cad2b267b99f7a44f09a0b74221
- request
- 92c34b06cabd711e02ac69f6883df33f312fd11449c796fd8a604841c9cefa61
- transaction
- eccd2ff13d2ef36997d4ce692f1aa3bba34fdf1db230d04a5610c20d12ce160ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62227
the chainentry 62227
- sealed to the entry before
- e98e331bbbb68518dd6835ed62abc9dbb0dff4b1a6ab06e31b00454d9172c7ea
- this leaf
- 518ad9f9b239d738ed253a7836366cc168436c4488f77dabfff06720f60a6d3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vjgQ9BmAefJ7GEEUHpzgpE3BfQJ2T2oe66BmJtAifeyLWnJrO9Yf45e2RLINkDXNhrL3Q3EB6r/+5XCmxR7pDA==