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
- 9da63a1fb746dd158d9a4253efb214778d52fc67f90a169e91bdb5254a27bc25
- request
- 3b8f806a0a7f244a5190e4eac36a59635a478a767afb36386ad2bf7dbaba45f2
- transaction
- 57cadae6f4d97ed4c48da7d0b88c04a36aece5ae5d20f3e0a2c909bd437ddcf6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8013
the chainentry 8013
- sealed to the entry before
- 711945a43d3d3defcdf41fb9554c4095254102386c573c6316dcee808bcf25a2
- this leaf
- 5a9900b5bf0a6a019d290c8ad54a205b10441718212b0cc4659e5b4cf532e517
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3c63THiQhusI4xI7phKBh9dUz+4xaTVv9C6Aw0v5JhuSKZrIJnJPf3fr4Qyfx041XhTJmc56nuAGNGcRKkolDA==