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
- 62dbbdac17e8ee8f262be8d8ee15e94e93e95c9773ab2797d8b999b95ef00f4d
- request
- 0964ff0f69113fceba8be0621bf4c37dfcf80f42a182b798150d06d7c80693fe
- transaction
- 03f91bc7c2cad9e0f6b8bb725cf81eb4835389d087bfe5e59005c6076734ae7ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54626
the chainentry 54626
- sealed to the entry before
- ed0bfee7fad3c6d6e137f789362a2bcac716ce52b6aea62b10ae9177a1a4506c
- this leaf
- fec239d566e519c2143f29ad8e368015075c5ef5e05f14b25dc7947eeca8c3e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U5IDRzo0S8fE6YDAksKoyD/YWvn/MzXmdSEsIMUpiNITtMGYN8zMMAGCQ4KYKrkjQybaskMtcbxkPVgpfAG6Cw==