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
- c9cf14d9798b96c211cc5420da91a5be389c05e9d4186e86b44d127b6ba80e3f
- request
- ddff11da7c556038459ce6490835c1669d49d6154af2a4b84d7740b93666140f
- transaction
- 2a8e189bc301ed7bb25eade06596ec93993a7dfc85a6352cdf96e99bad3901f4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77087
the chainentry 77087
- sealed to the entry before
- 351c6f3db5228e8ab835b08cc4aa946345c5db91530bf22e3dd685558aaf93e7
- this leaf
- 1e821f7f1107064667cca8108ad0b87ca9087314c7865b0d3f6fac2d5cd0083a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CoMwICjyEZg36WnRODd0kPVFxGjlA/u3AHLM3hfwE6NOPsCLkP1Zvi48CgDFqpY+mOGFkR59VG6kOMfxf8Z+Bw==