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
- b433926dfce0ee13d05133ebf78201b8c4a2376a2e95f75be0c90153548802ad
- request
- dba26c9e45dbaa6b68173f0de2e2a98a3e3e35ef40df77bd163ff2418e238094
- transaction
- 2de862804cbd277de78df45d1a0d1d2ef42e31e73ec699531c89844dd2708198computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57936
the chainentry 57936
- sealed to the entry before
- b65e0e6605d3428d73c681e69b2bcc7cc4ef7c2ecb40d1a71dc69bc4da28552e
- this leaf
- 8453e56a46582a8a9117ef15559695123b0041d44346db54890cdad36288948b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0rbLCHDZUH+BtGrhwce12ez7ekrmRnnZP4J0CEFvD0KMcN0VesLfy9WsriFgjx6MITBNClwU6Y0lyjA8qYxjDQ==