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
- 8d0d0ca923aacba65bac6fbf50218918fd843b1b3b580084d7ea29bb677d1658
- request
- ffbc8531f41fb447362ba1367a4140a07c381c47e0e882cea6f601adc77dd1b9
- transaction
- b26cb39919ccd8d14df2ceca16d1a53a2910db68996d1541ddc567be5afde530computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26728
the chainentry 26728
- sealed to the entry before
- 3610300fdb3b98986d0f74f94ab73449175c96f4bee7f7b5ba610ac136d94f47
- this leaf
- b6d021741c4289d928644109a0471ddeca1513c0ba28afeb98ed797031b5c10a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /VQajct33aHG8fEie9SI1HlF7cenT7xMvG9eaEZR8ED6c2TsmdBW87TJcCs9YVrAtGhpHtoHgx/ukmAEa7NAAA==