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
- f4cde284387e89f653790ee60d16a377f11e84a8a57743d217b1498594adcdae
- request
- 53bdb37df0bb8368161d01342e22fe3a51a04e3eba2c450fe960a43ae5b9bcc2
- transaction
- 1033e43330a35f74bc3731fec9f9348064ac3925dbf2fd5d07c6267dac639401computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18027
the chainentry 18027
- sealed to the entry before
- a43fce923868a1ed4b2403222a8d8321942252fc2a4f353a560d2f2e8fcf022c
- this leaf
- e6e008457279aff3f16e02dbb8bb878c440a3e2a2d25b3f2940469f456fb3a46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b5m5tu/P+T7IadDqzKztM8l2837Jiu8JMAkLK2mQAncowf/d7F7VHiMV3VaC8Mmj5z67AuS2uWNdaPM5zqkZCw==