Skip to content

PDF-SDK 2.4.1 is out.See what’s new

PDF-SDK
Banking and finance

PDF forms and signatures for banking apps

Account opening, loan applications and mandates — filled in, signed and checked inside your own app, on a tablet in the branch or a customer’s phone.

Start free trialTalk to sales

From application to signed agreement, in your app.

  1. Fill the application

    The customer fills the bank’s own PDF form; you prefill what you already know.

    doc.setFormValue("fullName", customer.name)Forms

  2. Sign with your keys

    A handwritten signature, or a digital signature made by your HSM or remote signing service.

    signDocument(editor, pdf, id, { reason })Signatures

  3. Lock and counter-sign

    Flatten the form so values can’t change; an officer counter-signs without breaking the first signature.

    doc.flattenForm()Forms

  4. Check before you file

    Verify every signature: who signed, when, and whether anything changed afterwards.

    verifySignatures(editor, bytes)Verify signatures

Code from the web API; the iOS and Android SDKs have the same document API.

Documents stay on the device

Customer documents are opened, signed and saved on the device — they never pass through a document server, and the branch keeps working when the network drops.

  • No document server, and nothing uploaded to us.
  • Works without a connection.
  • Signing keys stay in the device’s keystore or your own signer.
How we handle your data

Where the SDK stops

So you can plan for it before you build.

  • Scanned paper forms are images: PDF-SDK does not run OCR, so their text can’t be edited or searched.
  • A digital ID created on the device is self-signed. For signatures backed by a certificate authority, plug in your own signer.
  • Routing a document to the next signer, reminders and archiving are your app’s job — the SDK edits and signs the file you give it.

On every platform your users have

Banking and finance questions.

Ask about your project

Yes. The private key never enters the library: you supply a signer, the SDK hands it a SHA-256 digest and writes the signature it returns into the PDF.

No. Documents are opened, filled, signed and saved on the device. An online license check sends only the license key, the app’s identity and the SDK version.

Compliance belongs to your app and your processes, not to a component. PDF-SDK helps by keeping documents on the device and the signing keys under your control — it never receives document content.

More industries

Try it in your app.

A free trial unlocks every feature on every platform, in any app. Open a document today.

Start free trial Open the live demo

Talk to us

Questions about licensing, several apps, volume, or OEM and site terms — we will work out what fits.

Talk to sales