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
- 448f9556bbb6efd128343128943ca95502ae0d1894edd8d77e8e9e5423f416a2
- request
- 84f72abc5ddad716fc78936b6850266e56ed34fae88a938a2e7de09f03d4c0a2
- transaction
- 6cec2b3ad61dfd8f2522aea66bc69d9c775a38403d4bf5cf87e59a33295c2749computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64132
the chainentry 64132
- sealed to the entry before
- abecf660193c7490010353e25931d69b00ad2651146df0bca7bac464831df883
- this leaf
- 14bd3161b32105818447a57a92c1c897b5f0179976fe89cd4dc0bb4c77f20817
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MMLLuP5Dhm6DgBKqoCld4dfubU9CXn2DLSTiam6cf8GmZ4aKO0Nwyf6jeR942nnVYDpnzpAQDU9bkQ3tz2rxCQ==