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
- 753f1f8da2dbcaaffd74a2ef1d75e72375c4d20a917ce1fe618f9a8b2e2241d6
- request
- acb9b5c243c1c43fee4df0228dd631c597fc9e2585b14b2023813adb6bd1a57f
- transaction
- 778d4ceea050352b2765a9e25f5f402cb0f1eb6253f48fedb5381908705668a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1013
the chainentry 1013
- sealed to the entry before
- 40f3bf472e6c7c54773cac33fdd6ce2f09b015618f1250ebe99d3b1c2192f2de
- this leaf
- b91c6dd87235646ff8ca535b3beff0aee50c95bad9efa37a6fde632608bc6e28
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ugb233UAMjhhlp76RM3KNPXY8MwGnUYlalSnQeV9ERnqzk6rn66WpUaEFcpdTSSxymLQjCwXiGDgU91iELIKAQ==