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
- 41957f8179a6ffeb5a8af477701a38009237c4d808146e1edbcc04fa7f3ad3eb
- request
- c658e4d9c30afeb9c7ce5260d3799d5c0c1081644cf16cf56eb00edd3ff583e8
- transaction
- 5dd1d0b341e45397b5d929f0ea9985c67e7da7eea71223eea30c65f0a16758c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77630
the chainentry 77630
- sealed to the entry before
- 720e14ccaae858018c4d3e3b5bd730de57bf3f2f5fe3da3cc532e5d33115d339
- this leaf
- 1474fc8f53e1e09ba5fc3211c7b6a8c94c9352194b91586943cd742bb258d36c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NCEQp/41BmmB4B68l68wWA8kg4MnRGXBBYn8aovbc5gH0zFZd1bMO75xlh5QBipZxGGCw+slQOPzaDCWseL4Cw==