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
- bcb8b34c725a21e026d3c9695bd90cd1f8ef76a5f46cfd1c07d563c452212b6f
- request
- 856e4581d46205154eddbda666ead022fe2d14cbcf87159cec85aac760b5c755
- transaction
- fc1504ebb793a177d8f861f0913144e09fefdb02b2d72ed2d909dabfbd18e4e7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21630
the chainentry 21630
- sealed to the entry before
- dfbc5e550d1efead104124c90cad78771a3729f25cb01d141ddbae46738d3e45
- this leaf
- 27de26caf7595342163329744d396ba666491e8e7cf595ee55283e810c42bd44
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KFbX/XMqFysmUVlwDJ2dH72Rq8fPjmD2axeHe+bUn9PCGVeRNBu1VfHzRTV66vlJBprQBXod2zAnTz22MKtmBw==