Secure messaging-based delayed payout mediation with protective countermeasures
Abstract
An online system receives information about a first transaction including a destination account identifier and a payment amount from a source computing device. The online system sends the source computing device a deep link to a second application. The online system receives a confirmation including a transaction identifier from the second application. The payment was sent to an intermediate payment processor, which records the first transaction in a ledger in association with a source account identifier. The online system receives an instruction to reverse the first transaction. The online system sends an instruction to generate a second transaction to a source account of the source computing device including the transaction identifier and not the source account identifier to the intermediate payment processor. The online system receives a confirmation of the second transaction, where the intermediate payment processor queried the ledger using the transaction identifier to identify the source account.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method, comprising:
receiving, by an online system, from a first application running on a source computing device, information about a first transaction; sending, by the online system, to the source computing device, a deep link to a second application on the source computing device, the deep link comprising the information about the first transaction; receiving, by the online system, from the second application, a confirmation that the first transaction occurred comprising a transaction identifier for the first transaction, wherein the first transaction was recorded at a ledger of an intermediate payment processor; receiving, by the online system, an instruction to reverse the first transaction; sending, by the online system, to the intermediate payment processor, an instruction to generate a second transaction that comprises the transaction identifier of the first transaction and does not identify a source of the first transaction; and receiving, by the online system from the intermediate payment processor, a confirmation of the second transaction, wherein the intermediate payment processor performing the second transaction comprises querying the ledger using the transaction identifier of the first transaction.
2 . The method of claim 1 , further comprising:
sending, to a destination computing device, a notification that the first transaction is reversed.
3 . The method of claim 1 , wherein the instruction to reverse the first transaction is received from the source computing device.
4 . The method of claim 1 , wherein the instruction to reverse the first transaction is received from a destination computing device.
5 . The method of claim 1 , further comprising:
receiving, by the online system, from a new source computing device, information about a new transaction comprising a new destination account identifier; sending, by the online system, to the new source computing device, a new deep link to the second application on the new source computing device, the deep link comprising the information about the new transaction; receiving, by the online system, a confirmation that the new transaction occurred; and sending, by the online system, a new instruction to the intermediate payment processor to perform a transfer from an intermediate account to a new destination account identified by the new destination account identifier.
6 . The method of claim 5 , wherein sending, by the online system, the new instruction to the intermediate payment processor, is responsive to determining that a threshold amount of time has passed since the information about the new transaction was received.
7 . The method of claim 5 , wherein sending, by the online system, the new instruction to the intermediate payment processor is responsive to identifying the new destination account as a high trust destination account.
8 . A computer program product comprising a non-transitory computer-readable storage medium containing computer program code for:
receiving, by an online system, from a first application running on a source computing device, information about a first transaction; sending, by the online system, to the source computing device, a deep link to a second application on the source computing device, the deep link comprising the information about the first transaction; receiving, by the online system, from the second application, a confirmation that the first transaction occurred comprising a transaction identifier for the first transaction, wherein the first transaction was recorded at a ledger of an intermediate payment processor; receiving, by the online system, an instruction to reverse the first transaction; sending, by the online system, to the intermediate payment processor, an instruction to generate a second transaction that comprises the transaction identifier of the first transaction and does not identify a source of the first transaction; and receiving, by the online system from the intermediate payment processor, a confirmation of the second transaction, wherein the intermediate payment processor performing the second transaction comprises querying the ledger using the transaction identifier of the first transaction.
9 . The computer program product of claim 8 , further comprising:
sending, to a destination computing device, a notification that the first transaction is reversed.
10 . The computer program product of claim 8 , wherein the instruction to reverse the first transaction is received from the source computing device.
11 . The computer program product of claim 8 , wherein the instruction to reverse the first transaction is received from a destination computing device.
12 . The computer program product of claim 8 , further comprising:
receiving, by the online system, from a new source computing device, information about a new transaction comprising a new destination account identifier; sending, by the online system, to the new source computing device, a new deep link to the second application on the new source computing device, the deep link comprising the information about the new transaction; receiving, by the online system, a confirmation that the new transaction occurred; and sending, by the online system, a new instruction to the intermediate payment processor to perform a transfer from an intermediate account to a new destination account identified by the new destination account identifier.
13 . The computer program product of claim 12 , wherein sending, by the online system, the new instruction to the intermediate payment processor, is responsive to determining that a threshold amount of time has passed since the information about the new transaction was received.
14 . The computer program product of claim 12 , wherein sending, by the online system, the new instruction to the intermediate payment processor is responsive to identifying the new destination account as a high trust destination account.
15 . A system, comprising:
a computer processor; and a computer program product comprising a non-transitory computer-readable storage medium containing computer program code executable by the computer processor for:
receiving, by an online system, from a first application running on a source computing device, information about a first transaction;
sending, by the online system, to the source computing device, a deep link to a second application on the source computing device, the deep link comprising the information about the first transaction;
receiving, by the online system, from the second application, a confirmation that the first transaction occurred comprising a transaction identifier for the first transaction, wherein the first transaction was recorded at a ledger of an intermediate payment processor;
receiving, by the online system, an instruction to reverse the first transaction;
sending, by the online system, to the intermediate payment processor, an instruction to generate a second transaction that comprises the transaction identifier of the first transaction and does not identify a source of the first transaction; and
receiving, by the online system from the intermediate payment processor, a confirmation of the second transaction, wherein the intermediate payment processor performing the second transaction comprises querying the ledger using the transaction identifier of the first transaction.
16 . The system of claim 15 , the computer program code executable by the computer processor further for:
sending, to a destination computing device, a notification that the first transaction is reversed.
17 . The system of claim 15 , wherein the instruction to reverse the first transaction is received from the source computing device.
18 . The system of claim 15 , the computer program code executable by the computer processor further for:
receiving, by the online system, from a new source computing device, information about a new transaction comprising a new destination account identifier; sending, by the online system, to the new source computing device, a new deep link to the second application on the new source computing device, the deep link comprising the information about the new transaction; receiving, by the online system, a confirmation that the new transaction occurred; and sending, by the online system, a new instruction to the intermediate payment processor to perform a transfer from an intermediate account to a new destination account identified by the new destination account identifier.
19 . The system of claim 18 , wherein sending, by the online system, the new instruction to the intermediate payment processor, is responsive to determining that a threshold amount of time has passed since the information about the new transaction was received.
20 . The system of claim 18 , wherein sending, by the online system, the new instruction to the intermediate payment processor is responsive to identifying the new destination account as a high trust destination account.Join the waitlist — get patent alerts
Track US2022327524A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.