# Checkout flow with regards to encryption/decryption

**URL:** <https://www.ruby-forum.com/t/checkout-flow-with-regards-to-encryption-decryption/128506>\
**Category:** Rails\
**Created:** [February 8, 2008, 8:11am UTC](https://www.ruby-forum.com/t/checkout-flow-with-regards-to-encryption-decryption/128506 "2008-02-08T08:11:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dewie](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/ac8455/32.png) [@dewie](https://www.ruby-forum.com/u/dewie)\
**Post date:** [February 8, 2008, 8:11am UTC](https://www.ruby-forum.com/t/checkout-flow-with-regards-to-encryption-decryption/128506/1 "2008-02-08T08:11:10Z")

</div>

In the past I connect to the user to an SSL-secured portion of my site,  
asked for or updated their details. I used their credit card’s security  
code plus the customer’s ID in the database as the pass phrase to  
encrypt their credit cards (I used Rijndael for encryption).

I didn’t like doing it but I stored the customer’s security code in  
session for at least one action before decrypting the card and sending  
it to [Authorize.net](http://Authorize.net).

I’m curious to hear how others have handled the flow of checkout on  
e-commerce websites.
