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
- acb678cb717d006188519551b66d8982f199bcc2b6c9f4034e885be559c3a2fa
- request
- e0238a116066b7e90a42483f5128db3092d24afbb2706e5642dacc381435d196
- transaction
- c74db6a79f1b122109af238ac3cc5243272986f25876da1f011fea63fd512869computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51089
the chainentry 51089
- sealed to the entry before
- b6566d4a4aceee3d538452076d5916eba71c2e5fcc33d18a423e5eb9fc05086b
- this leaf
- bcdc7ac044875e37356cdebb0aeaf585b13580425e0ab0aa12178af9fca13741
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +dcUBv+8NR/uIhoaBqyqNbErDbEKnMM4xXUYYOcNTLp14EF24GgC5MsjVRTgXxwasTtGVr2mNp2pya9pnbxeAg==