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
- 2fce65df23daacbbf2ec79575d3c9ebd09678647b4e1775df17144d6d04a4700
- request
- a96aa43a1141fd42048a17584f440246570281253ce6b43497af368a1ac13da2
- transaction
- 027394225535d2a6ee3229a1d6bb45477c12a2bc41f4e887b144263dde9b335ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73916
the chainentry 73916
- sealed to the entry before
- 7c9528344432e0d0a903bd1b332d4856258d2ce2bec45830787a11efba3ac6b9
- this leaf
- 5011e37b58b953d2971e19fcc092bdd095598865d1150d2d8d875742820a9678
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8j5qqqhS09Oof7GUgtuM517RhWjO1m8bySUxhjlJHmnwnkYmCijGRVXWYjHGLA82mD9uWVjwWmSP+etLVKvvBw==