Sunteți pe pagina 1din 3

Standard Operating Procedure Template payulatam.

com

Document # Title: Print Date:


[ID] [FControl Monitoring] [Date]
Revision # Prepared By: Date Prepared:
1.0 [Erik Kiene Lopes] [Date]
Effective Date: Reviewed By: Date Reviewed:
[Date] [Reviewer’s Name] [Date]

Standard: Approved By: Date Approved:


[Standard, Law, [Approver’s Name] [Date]
or Regulation]

Purpose: Monitor merchants transactions in order to detect massive frauds and


improve anti-fraud rules.

Scope: não lembro o que é isso

Responsibilities: qual a diferença disso e do definitions?

Definitions:

Procedure:
1.0 [DOWNLOAD PROPER DATA FROM FCONTROL WITHIN THE DESIRED
PERIOD]

2.0 [RUN AN ANALISYS OVER THE DATA IN ORDER TO DETECT


OPPORTUNITIES FOR CREATING NEW FRAUD RULES]
3.0 [AFTER THE ANALISYS REPORT THE PAYMENTS THAT HAVE LESS
THAN 72H AND ARE MARKED AS FRAUD IN YOUR ANALISYS,
IN(COLOCAR NOME DO LUGAR ONDE REPORTA OS PAGAMENTOS),
SO THEY CAN BE DECLINED, NOT GENERATING A POSSIBLE
CHARGEBACK]
4.0 [GO TO YOUR MERCHANT’S PAGE IN FCONTROL AND SELECT
OPTIONS-> MANAGE ROWS, AND THEN UPDATE/DELETE THE
EXISTING RULE, OR CREATE A NEW ONE] DETALHAR MAIS
5.0 [UPDATE THE GOOGLE SHEET WHERE WE INSERT ALL CHANGES
ON OUR MERCHANTS RULES]
Effectiveness Criteria: Daqui pra baixo n entendi nada
References:

[ID] [Procedure Name] [Revision] page 1 of 3


Standard Operating Procedure Template payulatam.com

A. [STANDARD, LAW OR REGULATION]

B. [OTHER PROCEDURES, DOCUMENTS, ETC]

Forms/Records:
Satisfies
Form # Record/Form/Activity Name
Clause
Required by Standard
XXXXX Record
Other Forms/Records
XXXXX Record
XXXXX Record
XXXXX Record

Process Map:

[ID] [Procedure Name] [Revision] page 2 of 3


Standard Operating Procedure Template payulatam.com

Revision History:

Revision Date Description of changes Requested By


0.0 [Date] Initial Release

[ID] [Procedure Name] [Revision] page 3 of 3