Known Issues

Some transactions processed through the IUGU gateway take up to 20 minutes to update to

SETTLED

status after a payment is processed, which might cause the transaction to time out on the merchant's system.

Some merchants who process transactions through the IUGU gateway.

A delay in persisting payment reference data causes the initial payment confirmation status update from IUGU to fail.

None.

A defect is causing some invoices to remain in

PENDING

status instead of transitioning to

PAID

status after the cardholder completes payment.

Some merchants who use Invoicing.

Cybersource is updating the affected invoices to show the correct status.

Merchants who use Unified Checkout together with Decision Manager, specifically when a numeric-only value is entered in the first or last name field.

Authorization succeeds because the numeric surname is accepted during authorization processing; the rejection occurs only in the post-authorization scoring, creating a mismatch between the authorization result and the DM result that causes instant settlement to fail despite a successful authorization.

Ensure that customers do not enter a numeric-only value in the first or last name field, or disable the

After Authorization

Decision Manager scoring option.

A defect is causing some settled Prosa transactions to be missing the

Credit

button in the Business Center, which prevents merchants from creating a credit for the transaction in the Business Center.

Some merchants using the Prosa gateway, primarily in Latin America and the Caribbean (LAC).

During certain Prosa payment flows, the transaction's

BATCHED

status does not persist to the database. Because the transaction is not identified as batched, the

Credit

button does not appear.

Use the Virtual Terminal batch file upload feature to process the credit instead.

Some authorization requests sent to the

/pts/v2/payment

endpoint intermittently received 5xx errors during three brief intervals.

Some merchants who use Authorization.

A brief internal service error caused the failures.

None.