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
- b2df84e447c5b75484208607acba35aa58562d0172c71a5b00df2dccfe5ac260
- request
- e8cb3c373566f5f5d03afccb7e86010ee51a8213e5cee5283d8f4060e360744d
- transaction
- 3d726354e1da39b4b848f1372f5f10bfc55e43ae642b4fff26a7671a1f44bc00computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22441
the chainentry 22441
- sealed to the entry before
- 10d4aa624a3f06e30ed6502d6b52159a696cc3ddab29ced03abde0df1f11daf6
- this leaf
- c2e0c328f023c04e8eaa5d88cc6791b04aa45225c98b1ac648046314bcf87d40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- USetP1mipWmsEbIcKRvHdvRLlNK8o7qPsnEKuvya4XPYk/wdj6NmHLzZpqza+I0WeQ2RXChq+qzMdeKnpSB2Bg==