Handling credit card sources
Learn how Source objects created from credit cards function within the Digital River API.
Last updated
Learn how Source objects created from credit cards function within the Digital River API.
Last updated
In the Digital River API, sources created from credit cards are , , and . This means that customers aren't required to re-enter payment details before every payment; they are provided instant notification of a payment's approval status, and the amount charged to the card can be updated repeatedly throughout the checkout process.
The Sources API supports a .
To ensure that you remain PCI compliant, credit card Source objects are and then returned to your integration.
You must on your payment collection form to create a credit card source. You then and on it. Once a customer has supplied payment details, you pass the data to DigitalRiver.js to . We then return a source identifier to your integration.
You can either for use in the current Checkout and potentially reuse it in future payments or . In the latter case, the Source cannot be reused and will have a of consumed
once charged.
Credit card sources should be used shortly after they are created. This is because CVC data expires within a few minutes. Orders created with cards that lack CVCs are more likely to be declined and pose a greater fraud risk.
Once you have attached the Source to a Customer or directly to a Checkout, Digital River can then use it to create a when you .