Changelog

4.0.2

  • Replace a few instances of datetime.now with timezone.now to fix naive datetime warnings.

4.0.1

  • Fix bug in Internationalization string interpolation

4.0.0

  • Use Cybersource SOAP API for performing card authorizations

  • Support Bluefin encrypted card entry / swipe devices.

  • Improve Internationalization

3.5.0

  • Make payment methods create separate payment.Source objects per Reference number (!7).

  • Fix pate parsing bug which occurs during a spring-time daylight savings time transition.

3.4.1

  • Fix bug with missing payment token fields on REVIEW replies.

3.4.0

  • Adds support for django-oscar-api-checkout>=0.4.0

  • Fix error handling behavior in CyberSourceReplyView which often times lead to infinite loops.

3.3.2

  • Add management command for unreadable Secure Acceptance Profiles from the database: python manage.py remove_unreadable_cybersource_profiles

  • Add exception try/catch into SecureAcceptanceProfile.get_profile method to more gracefully handle Fernet decryption errors thrown when fetching a profile from the database.

  • Makes SecureAcceptanceProfile.get_profile method fall-back to Django settings when no readable profiles exist in the database.

  • Fix unit tests broken by an expired development key

3.3.1

  • Add order as a value for the CARD_REJECT_ERROR string template literal.

3.3.0

  • Use Cybersource’s reason_code field in addition to the decision field when deciding how to handle a response.

  • Move secure acceptance profile data into the database.

    • Profiles can be configured in the Django Admin interface. A default profile is created when running migrations based on the old environment variable settings.

    • Stores the profile secret key in the using Fernet encryption via django-fernet-fields. Therefore, you should declare a FERNET_KEYS setting in your project.

    • Since secure acceptable profiles are limited to a single domains for customer redirect pages, this change allows a single Django instance to serve multiple domains (by using multiple profiles).

3.2.3

  • Fix Django 2.0 Deprecation warnings.

3.2.2

  • Make it possible to use a placeholder ({order_number}) in settings.CARD_REJECT_ERROR.

3.2.1

  • Add better error handling to the Cybersource response view. Prevents exceptions when a customer refreshes and resends one of the payment POST requests.

3.2.0

  • Adds an order’s shipping method into calls to Cybersource. This field can then be used by decision manager to help make decision regarding order fraud.
    • Cybersource expects to receive one of the following values:

      • sameday: courier or same-day service

      • oneday: next day or overnight service

      • twoday: two-day service

      • threeday: three-day service

      • lowcost: lowest-cost service

      • pickup: store pick-up

      • other: other shipping method

      • none: no shipping method

    • You can configure the mapping of Oscar shipping method code to Cybersource shipping method codes using the CYBERSOURCE_SHIPPING_METHOD_DEFAULT and CYBERSOURCE_SHIPPING_METHOD_MAPPING Django settings.

  • Added exception handling and logging for bug sometimes occurring in the Cybersource reply handler.

3.1.5

  • Add support for Django 1.11 and Oscar 1.5

3.1.4

  • Improve testing with tox.

3.1.3

  • Upgrade dependencies.

3.1.2

  • Make DecisionManagerNotificationView directly set order status instead of relying on the set_status method. This avoids issues with order status pipelines.

  • Add optional CYBERSOURCE_DECISION_MANAGER_KEYS keys setting to allow token-based authentication on the decision manager web hook endpoint.

    • Default is disabled, which equates to disabled authentication.

    • To enable authentication, set it to a list of valid authentication keys/tokens.

    • When enabled, the DecisionManagerNotificationView view will inspect the key query parameter on incoming requests and compare it to the predefined keys in the setting. If it doesn’t match one of the keys, the request is aborted.

3.1.1

  • Make sure amounts sent to Cybersource are always properly quantized

3.1.0

  • Support flagging authorizations for review with Decision Manager

    • Transactions under review are marked with status REVIEW.

    • Adds new boolean property to payment.Transaction model: transaction.is_pending_review.

    • When handling an authorization that is pending review in Decision Manager, a note is added to the order.

3.0.5

  • Fix IntegrityError sometimes thrown when processing a declined payment.

3.0.4

  • Fix exception from typo in record_declined_authorization.

3.0.3

  • Fix case-mismatch of payment source types.

3.0.2

  • Add data migration to populate CyberSourceReply.order on rows from before 3.0.1.

3.0.1

  • Added foreign key from cybersource.CyberSourceReply from order.Order.

3.0.0

  • Change to two step SOP method with discrete get_token and authorization steps. This works around a bug in Cybersource’s code which will leave a pending authorization on a user’s card, even if the address verification or decision manager rejects the transaction. By doing the transaction in two phases, we can catch most AVN / DM rejections before the authorization is placed on the credit card. The downside is that the client must now perform 2 separate form posts to Cybersource.

2.0.0

  • Refactor as a plugin to django-oscar-api-checkout to eliminate code not related to Cybersource.

1.0.3

  • Make profile, access, and secret mandatory

  • Upgrade to django-oscar-api>=1.0.4 to get rid of the need for our custom empty basket check

  • Make test coverage much more expansive

1.0.2

  • README Updates

  • Added tests for FingerprintRedirectView

  • Fixed a bug in the img-2 redirect url

1.0.1

  • README Updates

1.0.0 (2016-01-25)

  • Initial release.