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
- 975fbfcdaa313a572f09584e3123d1a2b5820cd69debf3c823d956cad4653e99
- request
- 0b62accddbd0474cd5d98432a617c7fe789516078fbdc30fe9d251ce5a27557b
- transaction
- 785b3f90e39a3da2c42311e1f7e875a563df5ffd242e00d2ee9f44552c853914computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47693
the chainentry 47693
- sealed to the entry before
- 8adaf7282a2271a2de23f01c3ff2fda5765cbf3bed793ef2968cb88f1c115ce4
- this leaf
- 9e02f2847c5ab3aefe2b384bcf077ca04b93bd03bded4471782f7b68d06987bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CQSBijD7gbIAGbiwnX45ek51plgHUagIA+GzbAACtFA1N86xhbVV/8yp59WL0YmiEdniauX2Aooeg+5SXDJ2Bw==