Failed Credit Card Captures

The following explains how to resolve failed credit card capture issues:

Issue	Description
Technical	Credit card captures can fail because of technical issues with capture requests as indicated by the error message Capture rejected by card scheme because of a technical issue. Corrective action: None. Oracle Payment Cloud Service will try to fix the issue and re-capture the transaction. If the transaction is re-captured, the status of the payment becomes Sent for Settle, and you receive a webhook event with the following information: eventCode: CAPTURE success: true reason: Transaction Recaptured If the transaction is not re-captured within 10 days, contact the Oracle Support Team. If you use Pass-Through Payout, these errors will cause a settlement delay. The funds will only be paid out to you after the payment has been captured.
Shopper canceled the payment	If you accept recurring payments such as subscription payments or automatic top-ups, a guest may cancel a payment through their bank before you capture a payment. The following error message appears: Capture rejected by card scheme because the shopper cancelled the recurring payment through their bank. Corrective action: None. Neither you nor Oracle can recapture the transaction. Consider contacting the guest.
Account configuration error	A capture can fail if something is configured incorrectly in your Oracle Payment Cloud Service account. This affects all payments processed through your account, this may result in the same error for multiple transactions. The error message contains the raw error message sent by the card scheme: Capture rejected by card scheme: raw error message from the scheme (account configuration error). Corrective action: Contact the Oracle Support Team and provide: The PSP reference of the capture request. The error message. After you receive confirmation that your account configuration has been corrected, you can re-capture all payments that failed because of this issue.
Capture expired	A capture can fail if you submitted the capture request too late and it's no longer possible to recapture this authorization. A new authorization is required if you still want to get the funds for this payment. The error message contains the raw error message sent by the card scheme: Capture rejected by card scheme: raw error message from the scheme (capture expired). Corrective action: You can re-authorize the payment from your respective point of sale (for example, OPERA, xStore, or Cerner). Re-authorization is supported for a limited number of payment methods, and requires the user role Merchant re-authorize payments. To prevent this error in the future, you can: Make sure that you capture payments within the scheme expiry time. If you are using the pre-authorization flow, you can extend the authorization.
Capture can't be re-captured	Sometimes payments don't meet essential criteria to be captured, and card schemes don't allow these payments to be recaptured. The error message contains the raw error message sent by the card scheme: Capture rejected by card scheme: raw error message from the scheme. This capture cannot be re-captured. Corrective action: You should identify the cause of failure from the error message sent by the scheme and fix it from your side. This type of error can’t be fixed by Oracle. If it's a capture failure, and you need clarification about how to fix the error, contact the Oracle Support Team and provide: The PSP reference of the capture request. The error message. If it's a refund failure, then you can contact the guest directly to agree on a different payment method to refund the guest.