Healthcare transaction facilitation platform apparatuses, methods and systems
The Healthcare Transaction Facilitation Platform Apparatuses, Methods and Systems (“HTFP”) transforms payment file and EOP data inputs via HTFP components into ACH request, card generation request, card payment request, ACH CCD+ request, and EOP file outputs. A card generation request associated with a payment to a provider may be obtained via the card generating component via a network. A payment amount and a re-association trace number may be determined by parsing the card generation request. A card for the payment may be generated and the card may be associated with the payment amount and the re-association trace number. A card payment processing request associated with the card may be sent. The card payment processing request may be obtained via the card payment processing component. A Level 3 card payment request that includes the payment amount and the re-association trace number may be generated. A payment request route associated with the card may be determined and the Level 3 card payment request may be pushed via the payment request route.
1. A payment processing apparatus, comprising:
a memory;
a component collection in the memory, including:
a card generating component, and
a card payment processing component;
a payment settling component;
a processor disposed in communication with the memory, and configured to issue a plurality of processing instructions from the component collection stored in the memory,
wherein the processor issues instructions from the payment settling component, stored in the memory, to:
receive a payment settling request datastructure via the payment settling component;
determine, via processor, an ACH CCD+ payment amount and an ACH CCD+ re-association trace number by parsing the payment settling request, wherein the re-association trace number links an EFT payment with an EOP data file; and
provide, via a network, an ACH CCD+ payment request;
wherein the processor issues instructions from the card generating component, stored in the memory, to:
obtain a request to generate a payment card datastructure associated with the ACH CCD+ payment request to a provider via the card generating component via a network, wherein the request to generate a payment card datastructure is a request configured to generate the creation of a new payment card, and wherein the new payment card is any of: debit card, credit card, virtual debit card, virtual credit card, reloadable debit card, one-time credit card, one-time debit card;
determine, via processor, a payment amount and a re-association trace number by parsing the card generation request;
generate, via processor, a payment card datastructure for the payment;
associate, via processor, the payment card datastructure with the payment amount and the re-association trace number; and
send, via processor, a card payment processing request associated with the card;
wherein the processor issues instructions from the card payment processing component, stored in the memory, to:
obtain the card payment processing request via the card payment processing component;
generate, via processor, a Level 3 card payment request datastructure, wherein the Level 3 card payment request datastructure includes the payment amount and the re-association trace number;
determine, via processor, a payment request route associated with the card; and
pushing, via a network, the Level 3 card payment request datastructure via the determined payment request route.
2. The apparatus of claim 1 , further, comprising:
the processor issues instructions from the card generating component, stored in the memory, to:
configure the payment card datastructure to be usable with a specified set of allowed Merchant Category Codes.
3. The apparatus of claim 1 , wherein the payment card datastructure involves a single use card.
4. The apparatus of claim 3 , wherein generating the payment card datastructure includes generating a card number, a CVV, and an expiration date for the card.
5. The apparatus of claim 1 , wherein the payment card datastructure involves a reloadable card.
6. The apparatus of claim 5 , wherein generating the payment card datastructure includes generating a card number, a CVV, and an expiration date for the card.
7. The apparatus of claim 6 , wherein generating the payment card datastructure includes incrementing the CVV for a card to generate a unique identifier for the payment.
8. The apparatus of claim 6 , wherein generating the payment card datastructure includes incrementing the expiration date for a card to generate a unique identifier for the payment.
9. The apparatus of claim 1 , wherein the payment request route is one of: an acquirer, a payment network, and a virtual terminal.
10. The apparatus of claim 1 , wherein the Level 3 card payment request datastructure is sent from an issuer's server to a payment network's server.
11. The apparatus of claim 1 , wherein the Level 3 card payment request datastructure is sent from an issuer's server to an acquirer's server.
12. The apparatus of claim 11 , wherein the acquirer's server calculates an interchange rate associated with a card based on the provider's merchant identifier.
13. The apparatus of claim 11 , wherein the issuer and the acquirer are the same entity.
14. The apparatus of claim 1 , further, comprising:
the processor issues instructions from the card payment processing component, stored in the memory, to:
calculate an interchange rate associated with a card based on the provider's merchant identifier.
15. The apparatus of claim 1 , wherein
the processor issues instructions from the payment settling component, stored in the memory, to: send, via a network, an ACH CCD+ payment request, wherein the ACH CCD+ payment request includes the ACH CCD+ payment amount and the ACH CCD+ re-association trace number.
16. The apparatus of claim 15 , wherein the ACH CCD+ payment amount is the payment amount less a fee, and wherein the ACH CCD+ re-association trace number is the re-association trace number.
17. The apparatus of claim 15 , further, comprising:
the processor issues instructions from the payment settling component, stored in the memory, to:
update the provider's virtual terminal with details regarding the payment, wherein the details include the ACH CCD+ payment amount and the ACH CCD+ re-association trace number.
18. The apparatus of claim 1 , further, comprising:
an EOP file delivering component in the component collection, and
the processor issues instructions from the EOP file delivering component, stored in the memory, to:
select an EOP file associated with the re-association trace number;
determine the provider's EOP file delivery preferences; and
deliver the EOP file per the provider's EOP file delivery preferences.
19. The apparatus of claim 18 , wherein the EOP file delivery preferences include one of: FTP, email, clearinghouse, and provider pick-up.
20. The apparatus of claim 18 , wherein the EOP file is delivered within a specified time of the card generation request being sent.
21. The apparatus of claim 1 , wherein the payment is one of the plurality of payments in a batch of payments that are processed in aggregate.