8/26/2023 0 Comments Transaction central cyber sourcecommunicationError - An individual transaction was rejected by the processor.returnedItem - This will not show on an original transaction, but eCheck returns generate their own transactions with this status.failedReview - Final status of a transaction that fails review.underReview - Under manual review, will be approved or declined.I don't think these statuses need any further explanation, but let me know if I'm mistaken.įraud Detection Suite (FDS or AFDS) Specific Responsesīoth of these statuses indicate that a transaction is pending manual review by the merchant. I'm working towards making more of an official document for defining these fields, but I thought I would post what I have so far: ![]() * due to the two second timeout, fail-and-never-talk-to-you-again policy, plus having to rely on users to properly configure their settings* Is there really no way to pull just the 'pending' transactions from authorize, ignoring all the irrelevant `error`, `declined`, etc ones? It seems necessary for recurring billing - because otherwise, an app (in lieu of a transaction id) has no way of knowing if there's a problem with a subscription transaction, until enough time passes that you can safely assume it should have showed up in a settled batch. Do recurring billing transactions () even show up in the settled batches? ![]() Which of these go into a 'settled' batch? (`settlementError` AND `settledSuccessfully`? JUST `settledSuccessfully`? ) What's up with the last four statuses above? Should I expect those to change or not? The getUnsettledTransactionList just dumps the last 1000 'unsettled' transactions on your lap, including declined, error, etc - making it pretty unreliable, not mention you have to parse that junk. So, my questions are: The following appear to be 'pending' statuses: These appear to be 'final' and unchangeable: Yet, there's a multitude of possible transaction statuses. $this->assertTrue(is_array($transactions)) $transactions = $request->getTransactionsForDay(12, 8, 2010) $transactions = array_merge($transactions, $tran_list->xpath("transactions/transaction")) ![]() $tran_list = $request->getTransactionList($batch_id) $batches = $response->xpath("batchList/batch") $response = $this->getSettledBatchList(true, $firstSettlementDate, $lastSettlementDate) Public function getTransactionsForDay($month = false, $day = false, $year = false) The only practical way of pulling transaction status updates from authorize (without using their 'silent post' feature, which seems like a big bag of nightmares* ), is to get a batch list of settled transactions (for let's say a day) and then pull transaction lists for every settled batch. I'm having some trouble making sense of the Transaction Details API. This question was asked at StackOverflow but did not receive an answer so I am asking it here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |