Outbound Message Transfer : Payment Service

Outbound Mesage Transfer

HostedPCI understands that not all Merchants process the transactions for the credit card and Automated Clearing House (ACH) data that they collect and hence these cards need to be sent to a third – party to be charged. For these merchants, HostedPCI provides XML message transfer which can be used to send the payment details to a third party without the merchant requiring access to the full credit card PAN or ACH data.

The credit card or ACH data collection can be done by either using the HostedPCI iFrame, IVR or API depending on where the secure data is being captured. Once the Merchant is ready to send the credit card or ACH data for processing they simply call our Outbound Message Dispatch API action and easily send the payment details along with the customer details over to the third party of their choosing.

This service provides Merchants who collect and store credit cards or ACH data before sending them to the third party the ability to become PCI compliant without needing to change their payment flow. HostedPCI will collect and store the sensitive data to pass the data securely to the individuals who need it later.

icon HPCI service Outbound Message TransferDid you know?

The HostedPCI Message Transfer solution can also be used for API de-tokenization, which is de-tokenizing a credit card/ ACH data and returning the credit card/ACH data to the merchant upon request. This solution allows Merchants the ability to retrieve the credit card information when required for payment processing if they are unable to send the transaction through HostePCI. This allows the merchant to reduce their PCI scope by not collecting or storing the credit card and only accessing the credit card when required for payment.

If you do not see the third party you work with listed below call us to inquire about adding your third party for a small fee. You can also find more information on the technical implementation of this solution on our documentation page.

Case Studies

Follow a manual added linkFollow a manual added link

Please fill out the form below

This contact form is deactivated because you refused to accept Google reCaptcha service which is necessary to validate any messages sent by the form.