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
- 92687bf37f9191c23a486a303b553e3e636ba6ab9dd0dec0b61d54b3a3db751c
- request
- 94fb98759dcb3bcaca2acfd829e97e39100054af71a7af62f3b2db5c994fc0e8
- transaction
- 1482767f11835deee59cf7a75475854683b7b7d3ba7c31901f47d8c50c3fb999computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2813
the chainentry 2813
- sealed to the entry before
- 61ba81f40b3287d5c120ee34a7ac9c63cb901b9f4d9919fc94c2c0c82564c6c7
- this leaf
- b839dcb96a634add504e75b8a6401cbce8975d500d74be098c3916e55578dcdb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HR1Wk0rl3rb6QOx1le7CBjMJTw8dZs5/fdQGRcrPpQuH8oRexUnRhdWtEDZZ6ButcuRGEElBsOb8/zsboC+mDw==