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
- ed386019ccbd5a7c159224b3712376fe21533280e70ea9b332267aeb4f20892d
- request
- 273699f6a02027f40b85e4b9251b131e1198f97f7c6f5a609eab25d699cebb8b
- transaction
- 449318c28413a18a05f5d257909c3045df0ec6943f85d0080981e77f8df3055bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44658
the chainentry 44658
- sealed to the entry before
- 7594fa19e7ee7b52e2e71817236866d4150941d8df5916d59906d45fdde70b58
- this leaf
- 93bfed35c0d329c573ecbac8684a9e57ed691c8679212d52cb94484fc5c5683a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OC8K2cVJWqlJWfj9ttdpSj9VthMH/TeXoBcsdUj8skxO/NhCRMr8teApT4EE56r2k9iSa+tx4n1KjbDyaCtLDw==