Succeeded transactions
A succeeded transaction returns HTTP200 and response.success: true.
1
Mark the operation successful
Update your local record with the transaction outcome.
2
Store the transactionId
Save the
transactionId for reconciliation.3
Continue the workflow
Fulfill the order or move to the next step of your flow.
4
Reconcile later
Use the Query API or Backoffice to reconcile settled transactions.
Declined transactions
A declined transaction can return HTTP200 with response.success: false.
1
Do not fulfill the order
Treat the operation as unsuccessful.
2
Show the customer a clear message
Decline messages are generally safe to present in the UI.
3
Offer a retry path
Let the customer correct the issue or use another payment method.
4
Store the decline code
Record
code for analytics and support.Declines are expected payment outcomes. Do not treat them like infrastructure failures.
Failed transactions
A failed transaction indicates the operation did not complete as expected. Run rollback handling to prevent duplicate or inconsistent payment states.1
Do not fulfill the order
The final state is unclear.
2
Attempt a rollback
Use the rollback operation when the operation type supports it. See Timeout Handling.
3
Preserve the context
Store the original request, response, and
X-Request-ID.4
Investigate
Review the failure in server logs.
5
Escalate if unresolved
Contact Jupico support if the failure persists or the final state is unclear.
Implementation pattern
Related pages
Status Codes
Map HTTP status codes to integration behavior.
Error Handling
Split error handling between UI and server-side logic.
Error Codes
Look up any
code value returned by Jupico.Timeout Handling
Handle rollbacks after a request times out.

