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
- 3bf6b4f2b51b78b1ce03bb485aced0b2bcac8bfec2d7aa46c0fa6cc3ab85dc30
- request
- e2e55b3099d6e305458208644204eed2255af683c01bbe72ef622d95391cb272
- transaction
- d1583b9f64bc6491e6d8686fb591832d21e3ac0632056bb4d475f1df5fa06ac6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2802
the chainentry 2802
- sealed to the entry before
- 6fe337cc7268a77194c132f8c4870cde8283e78126f9757ef0b1066ef6b6f6e3
- this leaf
- e2f9ba3b53296a6e40a926dcf6c91bb66bbdb36509367dc41ee0dbb96fd1b4ad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 56Cteu8UAEHyj+3XY7dNfP63sA5M6z5G1bLW5/j6AwBNdsl4174aFWH6hLpqBGNQ/tD1lOFTkv0GDxsymz5LBg==