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
- 3bc01aa14bab9c479480854b484413dc4f566a7be72ebb5511eedf27b64b0748
- request
- 9ae3c6cb7a827c269500b76c865abda0705cb0086290ef138d6b0d837d206fd8
- transaction
- 451952233e3acb24ab100a0622ec13c97ecc5bf4cf23710981b2f706550389b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28775
the chainentry 28775
- sealed to the entry before
- 5cf8c8eca60f8eac1f5dd993dd5fa5d1c8f08c5f5ea1c946ccde8d0bcb135ae9
- this leaf
- c00bb882bc6f0222b695569713b70d673b6f88d2fc24d89915afb84f458e1ec1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VAjs5nJYSKyznX03uGcMV0QJ7Z3buH3q0ey9aldraBxYIel7PDJRVF9CR4ZCFmLbADjNn1/tZnxNrs85VcnzCQ==