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
- 20fc007c5155e0af88c764332bc8850acf8cbc7b942aeb1d11fc767d720e031e
- request
- 554af2d1ccdaf7819e0b60daa226716dac02d371edd8e4acda60b6180ed5a172
- transaction
- 50a27fcdb568a4839550b4b5d9a3164e8d5d90a20f274a6f1be3b5000bc2c19bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49223
the chainentry 49223
- sealed to the entry before
- 2be76bc77b54842bcbdb3bca46f4c1c1ed7100726f5bf26bc27cb037d26d6279
- this leaf
- ced4d919f6c4789d7f0d7b3d127603c7e10bc4dae16453a60117571d273d4c0d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Z4nl+AThTZEqVTOI5rz9E4rgbo8QF+AqHtJT0Dg9fN5/x1IkivWJ3KaLv60ASVlBRIjkWSLLNxGklIch4ZPsAQ==