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
- 3b119a6eeb09c0652581871c72b08470823880abe275bb4916d69685cb3c8bbd
- request
- 59aed1f67c8933fe032b4a3499c245b16bd24cd5269c0f8e53090d0903071e3b
- transaction
- a2e73398b2863406cadf89812c4dbf062a73db80f8db1ac5145697b5ecc65625computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61209
the chainentry 61209
- sealed to the entry before
- 3d8fcc215427f99fb8f670cae4948cb16a10ee1d63f9cc98cd36adce7f6a3378
- this leaf
- 0627e9d538526390a0ff1602c653a7367fbf3551cc5f28253c952cf986e4532c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RLbQR3qOm8N3ZIQeTffB1H0iKSTfs6aO/dVJjSYPxIRILWjeTj3StMu1sqhRFkXPmPT5MGIMUT4LbiA/kt/7Bw==