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
- 48e9f3a7c38a4c1845e3e8abd50292310b94acb99b3d67604539d68487f57777
- request
- 0adb37666b439a429b5f0ef83cf2c7752faf250824e388f4536ed585a20c25de
- transaction
- 38f27db5bfca8261faee258b83c47306afaf54e22f944e7ea4a7348340a7f5c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 776
the chainentry 776
- sealed to the entry before
- a77728ac8a3f5043e0bd1f719e92dc682f95ea4ac47f826831d467306162de18
- this leaf
- bc71dd5c8d7675a6f33abe625d7bcff032ab643418f4629884dfe09d9aab52df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nFBe1SsKIe9RZG3fhZDhLMUGZL2DDA8gHVgasMiuk9yQP1O3QgVoebCzOSn9ziKfb3jL2hJq9YJH2P7qX3HPBA==