Abstract: A system to process virtual credit card (VCC) payments automatically is provided. Electronic delivery of VCC payment information may be transferred as electronic data representing a VCC payment to the seller (e.g., an email). Data exchange methods for VCC payments include application programming interfaces (APIs), email, files, etc. Secure processing is provided via an environment that meets rigorous security standards (e.g., Payment Card Industry (PCI) data security standards). Credentials of the sending entity establish the context that allows the system to associate the data received with the correct buyer and seller. Authentication may be provided within the context of the data transferred. Authentication may also use the sender's email address to validate the sender using a digital signature of the email contents. The system may combine digital signature validation of an email with a validation of a sending entity using the DomainKeys Identified Mail (DKIM) email authentication protocol.

Abstract: A system to process virtual credit card (VCC) payments automatically is provided. Electronic delivery of VCC payment information may be transferred as electronic data representing a VCC payment to the seller (e.g., an email). Data exchange methods for VCC payments include application programming interfaces (APIs), email, files, etc. Secure processing is provided via an environment that meets rigorous security standards (e.g., Payment Card Industry (PCI) data security standards). Credentials of the sending entity establish the context that allows the system to associate the data received with the correct buyer and seller. Authentication may be provided within the context of the data transferred. Authentication may also use the sender's email address to validate the sender using a digital signature of the email contents. The system may combine digital signature validation of an email with a validation of a sending entity using the DomainKeys Identified Mail (DKIM) email authentication protocol.

Abstract: A system to process virtual credit card (VCC) payments automatically is provided. Electronic delivery of VCC payment information may be transferred as electronic data representing a VCC payment to the seller (e.g., an email). Data exchange methods for VCC payments include application programming interfaces (APIs), email, files, etc. Secure processing is provided via an environment that meets rigorous security standards (e.g., Payment Card Industry (PCI) data security standards). Credentials of the sending entity establish the context that allows the system to associate the data received with the correct buyer and seller. Authentication may be provided within the context of the data transferred. Authentication may also use the sender's email address to validate the sender using a digital signature of the email contents. The system may combine digital signature validation of an email with a validation of a sending entity using the DomainKeys Identified Mail (DKIM) email authentication protocol.

Abstract: A system to process virtual credit card (VCC) payments automatically is provided. Electronic delivery of VCC payment information may be transferred as electronic data representing a VCC payment to the seller (e.g., an email). Data exchange methods for VCC payments include application programming interfaces (APIs), email, files, etc. Secure processing is provided via an environment that meets rigorous security standards (e.g., Payment Card Industry (PCI) data security standards). Credentials of the sending entity establish the context that allows the system to associate the data received with the correct buyer and seller. Authentication may be provided within the context of the data transferred. Authentication may also use the sender's email address to validate the sender using a digital signature of the email contents. The system may combine digital signature validation of an email with a validation of a sending entity using the DomainKeys Identified Mail (DKIM) email authentication protocol.

Abstract: A computing device performs a method for predictive resource request hold and proactive hold resolution. The method includes: predicting a request for a resource from a requestor; predicting a hold on fulfilling the request; and determining a preventative action to minimize actualization of the hold on fulfilling the request. Predicting the request for the resource and predicting the hold can be performed using artificial intelligence. The preventative action can include temporarily increasing a credit limit for the requestor. Where the hold is actualized, the method can further include predicting a likelihood of the hold being released and determining whether to release the hold based on whether the likelihood of the hold being released exceeds a release threshold.