Главная страница


ru.nethack

 
 - RU.NETHACK -------------------------------------------------------------------
 From : SWW                                  2:5030/175.76  18 Oct 2002  22:43:33
 To : Ilya Teterin
 Subject : банкомат
 -------------------------------------------------------------------------------- 
 
 
  S>> p.s мудрый вопрос - нафига тебе бить молотком по банкомату, если
  S>> деньги уже сняты и карта вытащена? ты думаешь, что с твоего счета
  S>> деньги не снимут? :)))) Они уже сняты на определенном этапе.
 
  IT> Мне было непонятно, что происходит на том этапе, когда происходит
  IT> второй по счету сеанс связи с банком. Если деньги уже сняты - зачем
  IT> второй сеанс? Если еще не сняты - почему бы не стукнуть молотком?
  IT> Компетентный человек подсказал, что кроме "сняты" и "не сняты" есть
  IT> еще одно состояние денег - сам я до этого не додумался. Ему - спасибо.
  IT> Тебе - нет :)
 
 мне до этого нет никакого дела ;). я сам себе компетентный. состояние назвается 
 capture, если я не ошибаюсь. для того, чтобы понять что есть что и как оно
 работает, изучи биллинговую систему, сис-му онлайн платежей, тему "реал пластик"
 и т.п. потом можешь сказать спасибо, а можешь и не сказать (см. начало моего
 ответа)
 
 что такое capture, я тебе пожалуй из док Authorize'а дам... на почитай, поучись.
 (на примере кредитных карт)
 
 Auth-Capture
 Auth-Capture (Authorization-Capture) is the DEFAULT setting for all
 transactions, and obviously, the most common type of credit card transaction. In
 the absence of a transaction type specification, the transaction will be
 designated as Auth-Capture. In Auth-Capture, the transaction is sent through the
 Authorize.Net system for approval, the transaction is approved, the merchant is 
 notified of the approval, and the transaction automatically settles at the end
 of the business day (default of 6 P.M. Eastern Time or custom-set) without any
 further action by the merchant.
 
 Auth-Only
 An Auth-Only (Authorization-Only) transaction obtains an authorization for a
 certain amount on a customer's credit card without actually charging the card.
 Auth-Only transactions are useful for merchants who want to verify the validity 
 of a customer's credit card account before shipping products or accepting
 orders. This is similar to what hotels do when they collect a customer's credit 
 card number to make a reservation. The hotel processes an authorization-only
 transaction on the customer's credit card account to verify that the credit card
 number provided is legitimate. Auth-only transactions are not settled at the end
 of the day. Instead, they are kept within the current batch as an unsettled
 transaction until a Capture is selected in the Merchant Menu or a
 Prior-Auth-Capture transaction is sent through the system. If the money is not
 captured within 30 days, the Auth-Only transaction will expire.
 
 Prior-Auth-Capture
 A Prior-Auth-Capture transaction is used to capture funds authorized previously 
 using an Auth-Only transaction. Prior-Auth-Capture is really just an operation
 on an already existing transaction. Prior-Auth-Capture should ONLY be used on
 Auth-Only transactions processed using the system. If an authorization was
 obtained through ANY other means, you must use a Capture-Only transaction to
 capture these funds. If you wish to capture a different amount than what you
 previously authorized and you are processing a Visa transaction through Vital or
 FDC, you would need to enter a Prior-Auth-Capture transaction with the different
 amount, which is less than the originally authorized amount (you can't capture
 more than you originally authorized). If you need to capture a different amount 
 than what you previously authorized and you are not processing a Visa card
 through Vital or FDC, you must void the previous transaction and process a new
 transaction with the new amount. Prior-Auth-Capture transactions sent through
 scripts from the Merchant's site must include the merchant's password in the
 form.
 
 Capture-Only
 Capture-Only transactions are used when an authorization-only is obtained
 through any means other than the Authorize.Net system. Examples of this are
 phone authorizations, where an authorization code is received but the credit
 card is not yet charged. Merchants may use this authorization code to process a 
 Capture-Only transaction and capture the authorized funds. Normally this feature
 is not used for submitting transactions from your Web site. It is mainly used
 through Virtual Terminal.
 
 Credit
 All credits issued must adhere to the following criteria. Credits can only be
 issued to a credit card used for a previous settled transaction where the credit
 card was charged for purchases through your Authorize.Net Payment Gateway
 account. You cannot issue credits against transactions that failed, were
 declined, or were submitted as Authorization-Only transactions. The sum total of
 the credits issued to a credit card cannot exceed the amount of the transaction 
 originally charged to that card. Credits are not processed in real time, but are
 submitted at settlement time with other transactions. Credits are not processed 
 in real time, but are submitted at settlement time with other transactions.
 
 Void
 Voids are performed on existing transactions that have yet to be settled.
 Auth-Capture, Auth-Only and Credit transactions that have yet to settle in the
 current batch may be voided. Voiding a transaction prevents a charge to a credit
 card/bank account from occurring. Void transactions sent through scripts from
 the Merchant's site must include the merchant's password in the form. IMPORTANT:
 You CANNOT void a transaction that has already been settled. Instead, you must
 issue a Credit or initiate a new transaction for further settlement.
 
 Со всяческими регардами и прочим, SWW..
 +++ [Love Music]  [Crack Da World]  [Love girlz]   sww_@mailru.com !!!
  * Origin: В ком юмор вызывает зло - тому с умом не повезло! (2:5030/175.76)
 
 

Вернуться к списку тем, сортированных по: возрастание даты  уменьшение даты  тема  автор 

 Тема:    Автор:    Дата:  
 банкомат   Ilya Teterin   14 Oct 2002 10:29:30 
 банкомат   SWW   18 Oct 2002 13:13:04 
 банкомат   Ilya Teterin   18 Oct 2002 14:09:01 
 банкомат   SWW   18 Oct 2002 22:43:33 
 банкомат   Ilya Teterin   20 Oct 2002 17:47:38 
 банкомат   Dmitry Radishev   20 Oct 2002 10:53:53 
 банкомат   Ivan Bessarabov   21 Oct 2002 01:42:01 
 банкомат   Sergey Teryoshkin   18 Oct 2002 23:49:17 
 банкомат   Nikolaj Degtjajrev   19 Oct 2002 13:21:34 
 банкомат   Sergey Teryoshkin   20 Oct 2002 02:53:49 
 Re: банкомат   Andrey Zolotnicky   20 Oct 2002 10:14:44 
 банкомат   Sergey Teryoshkin   20 Oct 2002 17:51:52 
 Re: банкомат   Andrey Zolotnicky   20 Oct 2002 18:43:52 
 банкомат   Nikolaj Degtjajrev   20 Oct 2002 22:50:53 
 банкомат   Vladimir Skrobot   20 Oct 2002 18:58:13 
 банкомат   Nikolaj Degtjajrev   20 Oct 2002 22:46:48 
 банкомат   Sergey Teryoshkin   23 Oct 2002 12:10:31 
 банкомат   Nikolaj Degtjajrev   23 Oct 2002 21:47:38 
 Re: банкомат   Sergei Tchekantsev   15 Nov 2002 00:15:40 
 банкомат   Sergey Teryoshkin   16 Nov 2002 14:57:28 
 банкомат   Sergey Ternovykh   18 Oct 2002 22:46:20 
 Re: банкомат   Andrey Zolotnicky   19 Oct 2002 09:57:15 
 банкомат   Sergey Ternovykh   19 Oct 2002 15:27:52 
 Re: банкомат   Andrey Zolotnicky   19 Oct 2002 19:08:20 
 банкомат   Sergey Ternovykh   19 Oct 2002 21:22:28 
 Re: банкомат   Andrey Zolotnicky   20 Oct 2002 10:26:23 
 банкомат   Nikolaj Degtjajrev   19 Oct 2002 22:29:34 
 банкомат   Nick Lepehin   20 Oct 2002 01:04:36 
 банкомат   Igor Shkodyrev   19 Oct 2002 00:26:24 
Архивное /ru.nethack/40073db09050.html, оценка 2 из 5, голосов 10
Яндекс.Метрика
Valid HTML 4.01 Transitional