Systems and methods for secure transfers

1 . A method for a secure transaction comprising:

receiving a transaction request comprising payment information and an identification of a shared secret, at a payments platform executed by a server and from a sender interface executed on a sender's device;

determining to generate a link based on the receiver not being in an alias directory;

generating, at the payments platform, a link with a unique payment identification token specific to the transaction request only once the receiver has answered a shared secret request with the shared secret, the unique payment identification token being associated with a single transaction and valid only within a pre-defined expiry window;

sending the link with the unique payment identification token to a receiver;

receiving an API call when the link is activated by the receiver using a receiver interface executed on a receiver's device, wherein the API call occurs via HTTPS;

in response to the payments platform determining the link is activated, sending available payment details to the receiver and a request for a receiver detail via the API call and relegating sensitive institutional details, including account numbers, to secured channels of the payments platform;

receiving the receiver detail;

determining a transaction risk assessment score based on the payment information and the receiver detail;

recording, to a database, a payment route associated with the payment and a risk transaction score of the payment route;

based on the transaction risk assessment score exceeding a threshold, executing a payment according to the transaction request; and

sending the risk transaction score of a payment route of the transaction request to a customer and storing the risk transaction score in the risk system database of a financial institution.

2 . The method of claim 1 , further comprising comparing a payment method among available options and choosing a least expensive payment method for the transaction.

3 . The method of claim 1 , further comprising wherein determining the risk transaction score comprises using information of one or more of a sender and a previous transaction pattern.

4 . The method of claim 3 , further comprising, if the risk transaction score is below the threshold, retrieving one or more of: an identity document, a customer and risk system report of the sender or the receiver, and additional identifying information; and re-calculating the risk transaction score after the retrieval.

5 . A system for conducting a secure transaction comprising at least one computing device including a processor, the processor configured to execute instructions to:

receive a transaction request comprising payment information and an identification of a shared secret from a sender interface executed on a sender's device;

determine to generate a link based on the receiver not being in an alias directory;

generate a link with a unique payment identification token specific to the transaction request only once the receiver has answered a shared secret request with the shared secret, the unique payment identification token being associated with a single transaction and valid only within a pre-defined expiry window;

send the link with the unique payment identification token to a receiver;

receive an API call when the link is activated by the receiver using a receiver interface executed on a receiver's device, wherein the API call occurs via HTTPS;

in response to the payments platform determining the link is activated, send available payment details to the receiver and a request for a receiver detail via the API call and relegating sensitive institutional details, including account numbers, to secured channels of the payments platform;

receive the receiver detail;

determine a transaction risk assessment score based on the payment information and the receiver detail;

record, to a database, a payment route associated with the payment and a risk transaction score of the payment route;

based on the transaction risk assessment score exceeding a threshold, execute a payment according to the transaction request; and

send the risk transaction score of a payment route of the transaction request to a customer and storing the risk transaction score in the risk system database of a financial institution.

6 . The system of claim 5 , the instructions further comprising to compare a payment method among available options and choosing the least expensive payment method.

7 . The method of claim 5 , the instructions further comprising wherein to determine the risk transaction score comprises using information of one or more of a sender and a previous transaction pattern.

8 . The method of claim 7 , the instructions further comprising to, if the risk transaction score is below the threshold, retrieving one or more of: an identity document, a customer and risk system report of the sender or the receiver, and additional identifying information; and re-calculating the risk transaction score after the retrieval.

9 . A non-transitory computer readable storage medium, including instructions stored thereon for a secure transaction, which when read and executed by one or more computers cause the one or more computers to perform steps comprising:

receiving a transaction request comprising payment information and an identification of a shared secret, at a payments platform executed by a server and from a sender interface executed on a sender's device;

determining to generate a link based on the receiver not being in an alias directory;

generating, at the payments platform, a link with a unique payment identification token specific to the transaction request only once the receiver has answered a shared secret request with the shared secret, the unique payment identification token being associated with a single transaction and valid only within a pre-defined expiry window;

sending the link with the unique payment identification token to a receiver;

receiving an API call when the link is activated by the receiver using a receiver interface executed on a receiver's device, wherein the API call occurs via HTTPS;

in response to the payments platform determining the link is activated, sending available payment details to the receiver and a request for a receiver detail via the API call and relegating sensitive institutional details, including account numbers, to secured channels of the payments platform;

receiving the receiver detail;

determining a transaction risk assessment score based on the payment information and the receiver detail;

recording, to a database, a payment route associated with the payment and a risk transaction score of the payment route;

based on the transaction risk assessment score exceeding a threshold, executing a payment according to the transaction according to the transaction request; and

sending the risk transaction score of a payment route of the transaction request to a customer and storing the risk transaction score in the risk system database of a financial institution.

10 . The steps of claim 9 , further comprising comparing a payment method among available options and choosing a least expensive payment method for the transaction.

11 . The steps of claim 9 , further comprising calculating a screening risk score using information of one or more of a sender and a previous transaction pattern.

12 . The steps of claim 11 , further comprising, if the risk transaction score is below the threshold, retrieving one or more of: an identity document, a customer and risk system report of the sender or the receiver, and additional identifying information; and re-calculating the risk transaction score after the retrieval.