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
- 61cbc6ca7806e80f831872b9708d581ee36086f768206fc092f81de25d9280a9
- request
- baaef45296cb4903263cc73625b571361b8f39b66850cf6a0d6e86b71e9763d5
- transaction
- 2f851ababd4e3924f04593de25ffe8904c527a4271a7ef0d03cceef230161b88computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51526
the chainentry 51526
- sealed to the entry before
- 48c8dc1426911e3dc5e99ef7d639871bb31f2469e8ddc7eae9b8e187f677f68b
- this leaf
- 1fb956ac7f488763f031792eebd491f2af140abc0843a3eeb1a065cd28291967
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /Es8spJHhJ1/DV/aUCRmAWY3y290GrYeBekDWqBWlo7HAP2bhepLNxkGcAlkFkJWwdxoTKPHtIt06hOmv1kVAg==