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
- 75db67259bbc5394793e1f0b5d44bfb9c64bbc5d4717921a04bfe9d1dad0e059
- request
- f5c438f73d2c9b5cb23886cd409b36bb3e70f0cc4a1e327839636e5896761895
- transaction
- cbce80dbedfc2136a9033b9cfbabee68c37ac1e790f1ddd436410060bfa557a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71513
the chainentry 71513
- sealed to the entry before
- 9750c7f867eb7ef5a5859bc87020cfdf7d6166908cde6d28e231dd3b12db2bd4
- this leaf
- 0a259661a32f784576a91ea7cf2ef3e0ef578c7204391d468da8581025791234
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ja0rZzq6Yxz4zECYWd7DM5CHDtdHiv99uOME4GwoRwlX3BXh28iQuG+edHoKaWJKDII/PWzl4YJPyJ1Lc+c+Dw==