The JustiFi gem provides a simple way to access JustiFi API for apps written in Ruby language. It includes a pre-defined set of modules and classes that are essentially wrapped versions of our API resources.
Add these lines to your application's Gemfile:
gem "justifi"
And then execute:
$ bundle install
The gem needs to be configured with your client_id
and client_secret
in order to access JustiFi API resources.
Set Justifi.client_id
and Justifi.client_secret
:
require 'justifi'
Justifi.client_id = 'live_13...'
Justifi.client_secret = 'live_TDYj_wdd...'
OR just use the Justifi.setup
method to set all at once:
require 'justifi'
# setup
Justifi.setup(client_id: ENV["JUSTIFI_CLIENT_ID"],
client_secret: ENV["JUSTIFI_CLIENT_SECRET"])
There are two ways to create a payment:
payment_params = {
amount: 1000,
currency: "usd",
capture_strategy: "automatic",
email: "example@example.com",
description: "Charging $10 on Example.com",
payment_method: {
token: "#{tokenized_payment_method_id}"
}
}
Justifi::Payment.create(params: payment_params)
payment_params = {
amount: 1000,
currency: "usd",
capture_strategy: "automatic",
email: "example@example.com",
description: "Charging $10 on Example.com",
payment_method: {
card: {
name: "JustiFi Tester",
number: "4242424242424242",
verification: "123",
month: "3",
year: "2040",
address_postal_code: "55555"
}
}
}
Justifi::Payment.create(params: payment_params)
You can use your own idempotency-key when creating payments.
payment_params = {
amount: 1000,
currency: "usd",
capture_strategy: "automatic",
email: "example@example.com",
description: "Charging $10 on Example.com",
payment_method: {
card: {
name: "JustiFi Tester",
number: "4242424242424242",
verification: "123",
month: "3",
year: "2040",
address_postal_code: "55555"
}
}
}
Justifi::Payment.create(params: payment_params, idempotency_key: "my_idempotency_key")
IMPORTANT: The gem will generate an idempotency key in case you don't want to use your own.
In order to create a refund, you will need an amount, a payment_id ( py_2aBBouk...
).
payment_params = {
amount: 1000,
currency: "usd",
capture_strategy: "automatic",
email: "example@example.com",
description: "Charging $10 on Example.com",
payment_method: {
card: {
name: "JustiFi Tester",
number: "4242424242424242",
verification: "123",
month: "3",
year: "2040",
address_postal_code: "55555"
}
}
}
payment_id = Justifi::Payment.create(params: payment_params).data[:id] # get the payment id
reason = ['duplicate', 'fraudulent', 'customer_request'] # optional: one of these
amount = 1000
Justifi::Payment.create_refund( amount: 1000, reason: reason, payment_id: payment_id )
All top-level API resources have support for bulk fetches via array
API methods.
JustiFi uses cursor based pagination which supports limit
, before_cursor
and after_cursor
.
Each response will have a page_info
object that contains the has_next
and has_previous
fields,
you can find more information about this on JustiFi's Developer Portal.
payments = Justifi::Payment.list
# pagination with end_cursor
query_params = {
limit: 15,
after_cursor: payments.data[:page_info][:end_cursor],
}
payments = Justifi::Payment.list(params: query_params)
refunds = Justifi::Refund.list
# pagination
refunds = refunds.next_page
refunds = refunds.previous_page
payment = Justifi::Payment.get(payment_id: 'py_xyz')
refund = Justifi::Refund.get(refund_id: 're_xyz')
Note: the term seller account has been deprecated and will be removed in future versions. Please use sub account instead
You can make requests using the Seller-Account
header (deprecated, use Sub-Account
header) in order to process resources as a seller-account.
seller_account_id = "acc_xyzs"
Justifi::PaymentIntent.create(params: payment_intent_params, seller_account_id: seller_account_id)
Any API resource using the seller_account_id
(deprecated, use sub_account_id
) variable will include the Seller-Account
header and be processed as the seller account.
You can make requests using the Sub-Account
header in order to process resources as a sub-account.
sub_account_id = "acc_xyzs"
Justifi::PaymentIntent.create(params: payment_intent_params, sub_account_id: sub_account_id)
Any API resource using the sub_account_id
variable will include the Sub-Account
header and be
processed as the sub account.
Justifi::SubAccount.create(params: { name: "Created from Ruby SDK" })
sub_accounts = Justifi::SubAccount.list
# pagination
sub_accounts = Justifi::SubAccount.list(params: {limit: 5})
sub_accounts = sub_accounts.next_page if sub_accounts.has_next
sub_accounts = sub_accounts.previous_page if sub_accounts.has_previous
To list archived sub accounts, use the optional status parameter set to archived
archived_accounts = Justifi::SubAccount.list(params: {status: "archived"})
sub_account = Justifi::SubAccount.get(sub_account_id: "acc_xyzs")
If you are using our hosted checkout solution, follow this to generate a session:
# create a payment intent (check params [here](https://developer.justifi.ai/#operation/CreateCheckoutSession))
py = Justifi::PaymentIntent.create(sub_account_id: "acc_xyz", params: {})
# create a session (check params [here](https://developer.justifi.ai/#operation/CreateCheckoutSession))
session = Justifi::CheckoutSession.create(params: {})
# use the session id to access your hosted checkout page at:
hosted_checkout_url = "https://hosted-checkout.justifi.ai/#{session.data.checkout_session_id}"
Webhooks are secured by signature verification. An encrypted header is sent as a POST to your API endpoint (JUSTIFI-SIGNATURE), which will need to be decrypted and verified with the signature secret provided. You can use the JustiFi Ruby gem to validate the signature.
received_event = { id: "py_..." } # JustiFi webhook event
signature = "2463896d3cb..." # justifi-signature header
timestamp = "1651076887..." # justifi-timestamp header
secret_key = "sigk_2..." # secret key used for this webhook
Justifi::Webhook.verify_signature(received_event: received_event, timestamp: timestamp, secret_key: secret_key, signature: signature) # valid or not
Follow the steps below to make a release:
lib/justifi/version.rb
bundle
Gemfile.lock
lib/justifi/version.rb
main
After this, the .github/workflows/build_and_release.yml
will tag and release
the gem to github packages.
Everyone interacting in the JustApi project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.