Omnikassa Payment method for Spree
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Bèr Kessels 8d0bad8ee8 Update 7 years ago
app Payment-method was not saved. Assigning this manually. 8 years ago
config Callbacks finished. 9 years ago
lib Load decorators from correct dir, now that engine code was moved. 9 years ago
script Scaffolded code 9 years ago
spec Return request and homecoming over HTTPS 8 years ago
.gitignore Ignore Session.vim 9 years ago
.rspec Scaffolded code 9 years ago
Gemfile Update to latest spree 1.0.x. 8 years ago
Gemfile.lock Update bundle after bump 8 years ago
LICENSE Scaffolded code 9 years ago Update 7 years ago
Rakefile Scaffolded code 9 years ago
Versionfile Scaffolded code 9 years ago
spree_omnikassa.gemspec bump version number 8 years ago


For a Spree omnikassa that supports Spree ~2.x, please see

A Spree payment method for the Dutch Rabobank Omnikassa.

It was developed for Anna Treurniet and mentioned in the whitepaper on my blog.

It was developed to “just work” and not more. It is unmaintained and might not work.

The reason for that is Spree’s lack of any kind of support for offsite payments. Omnikassa is offsite. And as such it needs to be hacked into Spree; with many ugly overrides. On said site, it works, but this plugin breaks many things, due to the hackish way it needs to override the checkout workflow.

  • Coupons break; you cannot have coupons.
  • You cannot run it togeter with other payment methods.
  • Somehow the user-registration breaks, you can only run with anon users and even then in the backend some sub-sub-menu throws a 500-error.
  • It is tightly coupled to Spree 1.0. And upgrading requires quit extensive hacks or re-doing parts of the decorators.

I am severely dissapointed in the stubborn nature of Spree in this. As such, I have no plans to upgrade this to a recent version. I have no plans to maintain it, untill maybe Spree becomes more of a DSL for e-commerce rather then a complete, turnkey solution with all sorts of assumptions. Assumptions such as “payments are always done through gateways”.


I had plans to maintain and continue this extension; Hence I started off the extension with Rspec-coverage. Feel free to fork and continue this extension and when doing so, consider updating or removing the RSpec specs.

Copyright © 2012 Bèr Kessels, released under the New BSD License