Apr 24 03:26:08 payments1005 gravy_gateway: 230388880:230388880.1 Unsuccessful createPayment response from gateway: failed : {"type":"error","code":"bad_request","status":400,"message":"Request failed validation","details":[{"location":"body","pointer":"\/NA","message":"There is no active payment service for this transaction.","type":"assertion_error"}]}
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | jgleeson | T387411 How will we expose payment processor errors/issues with gravy | |||
| Open | None | T392545 There is no active payment service for this transaction. response from gravy, do we want failmail? |
Event Timeline
Comment Actions
This means we haven't set up the payment service in the Gravy console. I saw a few of these when mistakenly testing live forms before adding in the "Connections" for the different back-ends.