Receipt PDFs in Rust

Why receipts become PDFs

A receipt is proof a payment happened, and customers attach it to expense claims. It has to survive being forwarded, printed and filed by someone who never had an account with you. That is the difference between a document and a view of a database, and it is why ecommerce and point-of-sale teams keep asking for this.

What a receipt has to carry

Before any of the code below matters, the template has to produce a document that is actually a receipt. These are the fields that make it one, and the ones a reader or an auditor will look for first.

• the payment reference from the processor, which is what a dispute is traced by
• the amount actually captured, which is not always the amount ordered
• the payment method, usually the card brand and last four digits
• the timestamp with a timezone, since expense systems reconcile by date
• the merchant legal name, which may differ from the brand on the site

The Rust implementation

reqwest is the client most projects here already have. The render happens in an axum handler returning a streaming Body, and you return the byte stream as an axum Body.

// Client built once at startup and shared. It is internally
// reference counted, so cloning is cheap; rebuilding it is not.
async fn receipt_pdf(
    State(state): State<AppState>,
    Path(id): Path<String>,
) -> Result<Response, StatusCode> {
    let html = render_receipt(&id).await?;

    let upstream = state
        .http
        .post("https://api.pdfpipe.xyz/v1/pdf")
        .bearer_auth(&state.pdfpipe_key)
        .json(&serde_json::json!({
            "html": html,
            "options": { "format": "A4", "printBackground": true }
        }))
        .send()
        .await
        .map_err(|_| StatusCode::BAD_GATEWAY)?;

    let stream = upstream.bytes_stream();
    Ok((
        [(header::CONTENT_TYPE, "application/pdf")],
        Body::from_stream(stream),
    )
        .into_response())
}

The CSS that makes a receipt page correctly

The layout problem specific to this document is that receipts are short and usually want a narrow page, so the default A4 canvas leaves an expanse of white unless the page size is set deliberately. These rules handle it.

/* A receipt on A4 is mostly white space. Set the page to the
   content, and let it grow only as far as the items require. */
@page {
  size: 80mm 200mm;
  margin: 6mm;
}

body { font-size: 11px; }

What goes wrong in Rust

Building a reqwest::Client per request rebuilds the TLS stack every time. Construct it once and share it; it is already internally reference counted and cheap to clone.

What people try first

Most Rust projects reach for headless_chrome, which is a thin wrapper over a browser you still have to ship and supervise. That works until it is running on more than one machine, at which point the browser becomes the thing you operate rather than the thing you use.

Where the receipt lives afterwards

Rendering is the short part. The customer keeps it, not you, and they submit it to an expense system months later. It has to be readable by software that never saw your site, which is why the amount and reference belong in selectable text rather than inside an image.

Getting the document right

• Check the amount paid and the payment reference, which is what an expense system matches against.
• Generation is triggered by a successful payment webhook, so size the timeout for that path rather than for a health check.
• Volume arrives in bursts, so queue the render rather than doing it inside the request that triggered it.
• Backgrounds are painted by default here, so a design that uses colour needs nothing set. Only an explicit print_background of false turns them off.

Frequently asked

Related

Other Rust documents, and the same receipt in other stacks.