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
- 20849d0be61cdd92fe720931fd112422ec2d49a70224a9fb82c744602d0631ba
- request
- 6e2ce9833477f3e9a915db8f288b21adc33edd4f98a67017d511571bb2302c1f
- transaction
- c06d7b54967559914044c75f2cc6ae9bbf234c29833a58223dcbf650086f09a5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74651
the chainentry 74651
- sealed to the entry before
- bd9f40cf819b8dfd47d513fe67a218e3e3fa1917de23b73214281caec9ae5688
- this leaf
- 84584ce647311604baad9265320a5a21d4546200d0369e77631d4d861a947be1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BsOzpk/QiHI5J6dvya2sUGs42c4kjCA++h+502LMc4tI/6giSbtVfWY/SZJN4IwkRXLHiCtjFhXJDSu1TklMBA==