RubyUniversign is a Ruby gem for interacting with Universign electronic signature API.
It ease requests to Universign API, documents uploads and following signature state.
This gem is not officialy made by Universign, but was originally created by CapSens for internal usage.
This gem currently integrate electronic signature service, but not other Universign services (timestamping and server stamp).
Add this line to your application's Gemfile:
gem 'ruby_universign', require: 'universign'
And then bundle
Or install it with:
gem install ruby_universign
And load it with:
require 'universign'
Configuration:
# if you're using Rails, put this in an initializer
Universign.configure do |config|
config.endpoint = 'your_universign_endpoint' # Required ...
config.login = 'your_login' # Required ...
config.password = 'your_password' # Required ...
config.proxy = 'your_proxy_uri:your_proxy_port' # Optionnal ...
config.timeout = 30 # Optionnal if you wanna change the default XMLRPC Timeout ...
end
Then, you can create a transaction like this:
document_from_url = Universign::Document.new(
name: 'my_contract.pdf',
url: 'https://www.orimi.com/pdf-test.pdf'
)
document_from_content = Universign::Document.new(
name: 'another.pdf',
content: File.open('spec/fixtures/universign-guide-8.8.pdf').read
)
signer = Universign::TransactionSigner.new(
first_name: "Signer's first name",
last_name: "Signer's last name",
email: '[email protected]',
phone_number: '0101010101',
success_url: 'https://google.com/',
signature_field: Universign::SignatureField.new(coordinate: [20, 20], page: 1)
)
transaction = Universign::Transaction.create(
documents: [document_from_url, document_from_content],
signers: [signer],
options: { profile: 'default', final_doc_sent: true }
)
transaction.url
# => "https://sign.test.universign.eu/fr/signature/?id=f052e35e-a792-4440-bb67-6b5c3f17aa30"
transaction.transaction_id
# => "9696179e-a43d-4803-beeb-9e5c02fd159b"
# reload transaction data from universign:
transaction = Universign::Transaction.new('9696179e-a43d-4803-beeb-9e5c02fd159b')
# was the transaction signed by the user ?
transaction.signed?
The gem also supports the updated way of creating multiple signature fields per document:
doc_1 = Universign::Document.new(
name: 'one.pdf',
content: File.open('spec/fixtures/universign-guide-8.8.pdf').read,
signature_fields: [
Universign::SignatureField.new(coordinate: [20, 20], page: 1, signer_index: 0),
Universign::SignatureField.new(coordinate: [80, 20], page: 1, signer_index: 0)
]
)
doc_2 = Universign::Document.new(
name: 'two.pdf',
content: File.open('spec/fixtures/universign-guide-8.8.pdf').read,
signature_fields: [
Universign::SignatureField.new(coordinate: [100, 120], page: 4, signer_index: 0),
]
)
transaction = Universign::Transaction.create(
documents: [doc_1, doc_2],
signers: [signer],
options: { profile: 'default', final_doc_sent: true }
)
It can be created with either your file's content or your file's url.
Nothing much to say here. It follows Universign's signature field.
You can pass the coordinates of the signature or the name of the field.
If the PDF already contains a named signature field, you can use this parameter instead of giving the coordinates (which will be ignored). If the name of this field does not exist in the document, the given coordinates will be used instead.
success_url
is where your user will be redirected after signing the documents.phone_number
is optional. If you don't specify it, Universign will ask the user for it at the time of the signature.email
is optional, unless you want to use transaction'sfinal_doc_sent
option (to send signed documents to user's email).
To start a transaction with Universign, you only require documents and signers.
Options are, as the name imply, optional ! Available options are (snake_case of Universign's names):
custom_id
description
handwritten_signature_mode
certificate_type
language
identification_type
handwritten_signature
profile
final_doc_sent
final_doc_requester_sent
chaining_mode
Default options are:
{
handwrittenSignatureMode: 1,
identificationType: 'sms',
language: 'fr',
certificateType: 'simple'
}
For more informations on theses options, see Universign's official documentation
Once your transaction is created:
url
is where you must redirect your users for them to signtransaction_id
is the id you must save to retrieve it later. You can request up-to-date informations from Universign withUniversign::Transaction.new(transaction_id)
.signed?
returns a boolean that tells you if the transaction is signed, or not !
As of September 25th 2018, all official Universign documentation can be found at https://help.universign.com/hc/fr/sections/360000148149-Guides-Universign.
After checking out the repo, run bin/setup
to install dependencies. Then, run rake rspec
to run the tests. You can also run bin/console
for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install
.
To release a new version, update the version number in version.rb
, and then run bundle exec rake release
, which will create a git tag for the version, push git commits and tags, and push the .gem
file to rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/CapSens/universign. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
The gem is available as open source under the terms of the MIT License.