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
- 7b15f0664225666be318c7a7684532cf90e3a51418347e1ddf438d4ed45be4d3
- request
- d0dd7ae21928233174986e692715be075ba380a2857d6e673d2f1971231b687c
- transaction
- d5849c59688223e2ea706b3b33268e328fb34a5ba51992438c41337d7dd62e78computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36104
the chainentry 36104
- sealed to the entry before
- b85b3bd9f7ed17b2d5a09dd354b525b99489323785fa839a9a3bd07af536ce2f
- this leaf
- 20c1c358e31591be310fc825b3c2c78251ad169b4ec7c57e0c344b6a9a01eb18
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UfzGdA+80H0zsMMdIZ5VybQ2bN4IIyqoDpWLY5VS0C98II28QEeJPA4FhU0WWedXu5jG83Qg2DbuaCCNdyAhCA==