Вы находитесь на странице: 1из 4

Tiltproof Incorporated Document No. Effective Date Revision Date Approval 5.10.

3 06/21/2007 GN

Payment Processor Reconciliation for Optimal

1.0 Purpose:

This document establishes how to handle payment processor reconciliation for Optimal.

2.0 Persons Affected:

1) Cashier Team Leads 2) Supervisors

3.0 Forms, Checklists, Flowchart:

1) Printable version: \\tpfs1nw\workflow$\HANDBOOK-CASHIER TL AND ABOVE\Print Versions\Cashier TL and Above Handbook\5.10.3 Optimal.doc

4.0 Policy:

A) Contact Information The merchant account is <https://admin.firepay.com/falcon/login.jsp> 1-514-380-2793 is Olga Argirious office phone number. Include David Quach <dquach@pocketkings.ie> on all important payment processor related emails (i.e. processor policy inquiries, replenishment requests).

B) When to use Account Lookups 1) Account look ups are performed to: verify the status of completed transactions on behalf of players confirm player contact information matches the owner of a processor account when fraud or invalid information is suspected 2) Players who are not from the United States are still eligible to withdraw to FirePay at this time. Processing to FirePay is no longer an option for American players All withdrawals processed to FirePay for players with addresses in the United States will show as "ProcessingFailed" in WAT after processing and will need to be failed by a Team Lead.

Tiltproof Incorporated

5.0 Procedure:

A) Transaction Search 1) Go to <https://admin.firepay.com/falcon/login.jsp> 2) Log in with the username and password 3) Select the Reports tab 4) Select the appropriate date range a) Due to the time zone difference, when searching transactions after 9 PM PST (which is 12 AM EST next day), the date ranges needs to be adjusted to reflect the correct date in the search function. 5) On the Activity Report, enter the Transfer IX followed by -00000000 next to Merchant Transaction ID (it is also possible to search by email address or account number) 6) Select Generate Report Valid requests will show on the generated page To view details of the transaction click on the blue Authorization status Fully Settled or Fully Batched. The transaction may also appear as Authorization Refused. 7) Select the blue Confirm. Number listed to confirm the owners full name and address B) ProcessingFailed Deposits 1) Open the Deposit queue in WAT 2) Select transactions with a ProcessingFailed status. 3) Look up the transaction in the payment processors merchant site as per A) Transaction Search.

4) a) Fully Settled or Fully Batched Enter appropriate Auth Code next to Auth Code 1: Notate FP DEP: approved by processor Select Accept Deposit b) Authorization Refused Fail the transaction in WAT by selecting the Fail tab Notate FP DEP: refused by processor c) Not found on Optimal site Fail the transaction in WAT by selecting the Fail tab Notate FP DEP: not found on processor
site

Tiltproof Incorporated C) ProcessingFailed Withdrawals 1) Open the Withdrawal queue in WAT a) Batch item processed successfully or Completed Enter the appropriate Optimal Transaction ID if available or type FP as the authorization code. Select Accept Deposit b) Authorization Refused Fail the Transaction in WAT by selecting the Decline tab, selecting Other for the Reason Code and leaving a note Optimal WD Failed c) Not found on Optimal site Fail the Transaction in WAT by selecting the Decline tab, selecting Other for the Reason Code and leaving a note
site. Optimal WD not found on merchant

2) If the withdrawal failed another one must be initiated manually. 3) Email the player wd.manual from Kana to let them know there was an error in their first transaction and we have resubmitted it. D) Manual Withdrawals 1) Find the player in WAT 2) Select W/D from the Player Shortcuts section.

3) Enter the amount of the withdrawal. 4) Select a Reason Code Presently there is only Other. 5) In the Note box explain why the withdrawal request is being manually initiated. 6) Double check the amount entered and the player ID. 7) Select Submit. E) Response Codes

Tiltproof Incorporated 1) Response Code 221 with sub response code 1010 a) The transaction was failed due to CVS failure (the security # on the back of a credit card). The amount is reserved on the credit card even though the transaction fails b) Customer should contact Optimal at Support@OptimalPayments.com to release the hold on the transaction and have the funds returned to the Visa card 2) Response code 34 a) This is an error message returned from the bank, who failed the transaction, stating that this transaction was declined b) With sub-response code 1005, the transaction could have been failed by customer's bank due to the following reasons: Credit card has insufficient funds Bank policy against online gaming Anti-fraud algorithm. c) Often, banks will put a hold on the transaction and it could take 2-4 weeks to be released even though the transaction was declined. This is an issue with the customer's bank. Full Tilt Poker failed the transactions based on the information provided. We are not responsible for reversing the transactions and crediting their Full Tilt Poker account. We will not override a bank's decision. F) Contacting the Processor Send reversal status and confirmation inquiries to <olga@FireOneGroup.ie> from the <Operations@fulltiltpoker.com> email address. CC <fraudoperations@fulltiltpoker.com> for account status inquiries (not reversal requests, etc.). BCC: <scsr@tiltproof.ca> on reversal and inquiry requests. Include David Quach <dquach@pocketkings.ie> on all important payment processor related emails (i.e. processor policy inquiries, replenishment requests).

6.0 Definitions: 7.0 Revision History:

Оценить