Push payment decision routing
In an example embodiment, a method for push payment decision routing in relation to a transaction is provided. An example method comprises issuing a virtual payment identifier to a mobile device and receiving payment rules from a mobile device. The user-defined rules include parameters for invoking at least one push payment to be made via the virtual payment identifier for the transaction. Instructions to implement or pay for the transaction as a pull payment are received and, based on the rules, the transaction is completed or paid for a push payment.
1. A method comprising:
receiving, by an electronic device, a virtual identifier issued by one or more servers;
identifying, by the electronic device, a rule that is associated with the virtual identifier and that includes one or more parameters defining an invocation of a push operation instead of a pull operation; and
causing, by the electronic device and based on the rule, the one or more servers to complete a transaction as the push operation instead of as the pull operation by shifting performance of verification from being performed by the one or more servers verifying, based on a card verification number, that a user of the electronic device is allowed to complete the transaction to being performed by the electronic device verifying a biometric identifier of the user of the electronic device.
2. The method of claim 1 , further comprising:
identifying an operation classifier associated with an electronic transfer of data,
wherein the rule is configured for a plurality of electronic transfers of data associated with the operation classifier, and
wherein completing the transaction comprises completing the electronic transfer of data as the push operation based further on the operation classifier.
3. The method of claim 1 , further comprising:
determining that the rule is not satisfied when an operation amount associated with an electronic transfer of data is above an operation amount threshold; and
in response to the determining that the rule is not satisfied, causing the electronic transfer of data to be completed as the pull operation and not the push operation.
4. The method of claim 1 , wherein the rule is configured by the user of the electronic device.
5. The method of claim 1 , wherein a first authorization instrument is associated with the pull operation.
6. The method of claim 5 , wherein completing the transaction comprises:
identifying a second authorization instrument associated with the push operation; and
completing the transaction as the push operation based on the second authorization instrument.
7. The method of claim 1 , wherein the virtual identifier is a virtual card or a token.
8. The method of claim 1 , further comprising:
storing, in the electronic device, the virtual identifier in association with a plurality of rules that include the rule.
9. The method of claim 1 , further comprising:
changing the rule based on inputs received via an interface of the electronic device.
10. The method of claim 1 , further comprising:
changing the rule based on inputs received via a web interface associated with the one or more servers.
11. The method of claim 1 , wherein the pull operation requires use of a scripting library associated with the one or more servers.
12. The method of claim 1 , wherein the rule includes an instruction to process data received for the pull operation as the push operation.
13. The method of claim 12 , further comprising:
providing, for display, an interface for configuring the one or more parameters to invoke the instruction when one or more conditions are satisfied.
14. A system comprising:
at least one memory storing instructions; and
one or more hardware processors communicatively coupled to the at least one memory and configured by the instructions to perform operations comprising:
receiving, a virtual identifier issued by one or more servers;
identifying a rule that is associated with the virtual identifier and that includes one or more parameters defining an invocation of a push operation instead of a pull operation;
causing, based on the rule, a transaction to be completed as the push operation instead of as the pull operation by shifting performance of verification from being performed by the one or more servers verifying, based on a card verification number, that a user is allowed to complete the transaction to being performed by the system based on verifying a biometric identifier of the user.
15. The system of claim 14 , wherein the operations further comprise:
identifying an operation classifier associated with an electronic transfer of data,
wherein the rule is configured for a plurality of electronic transfers of data associated with the operation classifier, and
wherein completing the transaction comprises completing the electronic transfer of data as the push operation based further on the operation classifier.
16. The system of claim 14 , wherein the operations further comprise:
determining that the rule is not satisfied when an operation amount associated with an electronic transfer of data is above an operation amount threshold; and
in response to the determining that the rule is not satisfied, causing the electronic transfer of data to be completed as the pull operation and not the push operation.
17. The system of claim 14 , wherein a first authorization instrument is associated with the pull operation.
18. The system of claim 17 , wherein the operations further comprise:
identifying a second authorization instrument associated with the push operation; and
completing the transaction as the push operation based on the second authorization instrument.
19. The system of claim 14 , wherein the rule includes an instruction to process data received for the pull operation as the push operation.
20. A non-transitory computer-readable medium comprising instructions that, when executed by a hardware processor of a machine, cause the machine to perform operations comprising:
receiving a virtual identifier issued by one or more servers;
identifying a rule that is associated with the virtual identifier and that includes one or more parameters defining an invocation of a push operation instead of a pull operation;
causing, based on the rule, a transaction to be completed as the push operation instead of as the pull operation by shifting performance of verification from being performed by the one or more servers verifying, based on a card verification number, that a user is allowed to complete the transaction to being performed by the machine verifying the user.