Revision history for CyberSourceMigrationNotes
Additions:
CategoryITMisc
Deletions:
Additions:
<<See also CyberSource<<::c::
Additions:
~- Each profile is associated with one or more secret keys and access keys. Make sure you are using the right keys. You can find the keys in the profile security settings on the CyberSource site.
Deletions:
Additions:
~- When testing, use the Transaction Search->Secure Acceptance Search on the CyberSource dashboard to check for errors.
Additions:
CyberSource, the payment processor used by PVS, is forcing its users to migrate from HOP (Hosted Order Page) to SA (Secure Acceptance) Web/Mobile. Here are the pertinent resources that were used in transitioning the PVS donate, help-us (three-way) and API payment pages to SA:
~- SA now allows for the creation of multiple profiles (which you include as an attribute of the POST made during payment). This removed the need for application-specific parameters such as email addresses. We are using PVSDONA for PVS donations (made through the donate or help-us pages), and PVSAPIR for API registrations.
~- SA now allows for the creation of multiple profiles (which you include as an attribute of the POST made during payment). This removed the need for application-specific parameters such as email addresses. We are using PVSDONA for PVS donations (made through the donate or help-us pages), and PVSAPIR for API registrations.
Deletions:
~- SA now allows for the creation of multiple profiles (which you include as an attribute of the POST made during payment). This removed the need for application-specific parameters such as email addresses. We are using PVSDONA for PVS donations (made through the donate or helpus pages), and PVSAPIR for API registrations.
Additions:
~- Each profile is associated with one or more secret keys and access IDs. Make sure you are using the right keys. You can find the keys in the profile security settings on the CyberSource site.
Additions:
~- SA now allows for the creation of multiple profiles (which you include as an attribute of the POST made during payment). This removed the need for application-specific parameters such as email addresses. We are using PVSDONA for PVS donations (made through the donate or helpus pages), and PVSAPIR for API registrations.
