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
- f7f2c965b4344b0287df539e5864412c1d555382f1330f429a9142c961b2bc4f
- request
- 340a2a1d0c64c88b0e610118d6be8f864c9dc11f2ffcaee2a220f3d961d9feec
- transaction
- 7b51a1f23ec2e8e5cc48b52c3aa0a218411457ab08c94cc5049f25efeef2b3c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33653
the chainentry 33653
- sealed to the entry before
- 1e7f3adc0cca6b90e860ec5e0a2b72128b844a9350041293919cd3f8a385639a
- this leaf
- 305fbc0af8d98378cbc6ba311a24342cf69d56e9e733e99266efade8203176a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JrgQIoiZPUo4PCho6ocYyOV62Hx5olaZDFry3eV27V3qhrK6upLj+TI50TRFNMJACd6FW43PFEt0c0eXJj4AAA==