Module: DCAS

Defined in:: lib/dcas/response.rb,
lib/dcas.rb,
lib/dcas/payment.rb,
lib/dcas/ach_return.rb,
lib/dcas/ach_response.rb

Overview

__ Documentation __ CreditCard returns are pretty straightforward. They’re handled by just this class here, DcasResponse. ACH returns come in two stages, and they have to be handled differently, so they’re defined in DcasAchResponse and DcasAchReturn.

A DcasResponse object has a status. That status can be one of [‘I’, ‘A’, ‘G’, ‘D’] These map to a GotoTransaction’s statuses, which are as follows:

'R' => Received
'A' => Accepted
'G' => Paid
'D' => Declined
'E' => Processing Error

Notice that the three with the stars map directly to three of a DcasResponse object’s statuses. The fourth status, ‘I’, is used to denote an Informational record. These records are never intended to state whether a payment was accepted, declined, or paid, but rather to provide important information back into the system about an account, such as information that needs to be updated soon.

Defined Under Namespace

Classes: AchPayment, AchRefund, AchResponse, AchReturn, Client, CreditCardPayment, CreditCardRefund, Payment, PaymentBatch, Response

Constant Summary collapse

TESTING =

false

BUCKET_HOST =

'ftp.ezpaycenters.net'

DEFAULT_OUTGOING_BUCKET = The return files coming back to us.

'outgoing'

DEFAULT_INCOMING_BUCKET = The payment files we’re sending TO dcas.

'incoming'

STAGING_BUCKET =

'staging'

DEFAULT_CACHE_LOCATION =

'EFT'

Class Method Summary collapse

.parse_response_file(filename_or_content) ⇒ Object

Parses the responses from a response file and returns an array of DCAS::Response objects.

Class Method Details

.parse_response_file(filename_or_content) ⇒ `Object`

Parses the responses from a response file and returns an array of DCAS::Response objects.



13
14

# File 'lib/dcas.rb', line 13

def parse_response_file(filename_or_content)
end