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
- 7653a176019c9c02a7922a5f3a239ae278094b463abf049bb737a96d4437799c
- request
- 9c08aa2589d04226993e25eba151bd3ef4ad7da32503764ba7c38d19ae513f3e
- transaction
- 08f175ab36f6eb6298057e7f899f73686265ff019bc279203d32534a0caac2e6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39265
the chainentry 39265
- sealed to the entry before
- bb723282de11405f032820b6bc300cb602a53eb387cdb47c476a91d8790ea04d
- this leaf
- 595ebdea7ad9fa490daa95c41144b8278a341482b146a0762885d5d01bafcc83
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kuRrbnxer3Dmw7KCiLuWIexl82PKfJKUL8AUViAHpBCGHTkHDcIQF/hytAFApC4aQcagWBiLyGHyQhL/+hxCAA==