...
S. No. | Resource | HTTP Operation | Endpoint | Mandatory | Scope | Grant Type | Message Signing | Idempotency Key | Request Object | Response Object |
2.1 | domestic-payment | POST | POST /domestic-payments | Mandatory | payments | Authorisation Code | Signed Request Signed Response | Yes | OBWriteDomesticPaymentRequest | OBWriteDomesticPaymentResponse |
2.2 | domestic-payment | GET | GET /domestic-payments/{DomesticPaymentId} | Mandatory | payments | Client Credentials | Signed Response | No | NA | OBWriteDomesticPaymentResponse |
2.3 | Paymentpayment-details | GET | GET /domestic-payments/{DomesticPaymentId}/payment-details | Optional | payments | Client Credentials | Signed Response | No | NA | OBWritePaymentDetailsResponse |
...
This is done by making a POST request to the domestic-payments endpoint
This request is an instruction to the ASPSP to begin the single domestic single immediate payment journey. The domestic payment must be submitted immediately, however, there are some scenarios where the domestic payment may not be executed immediately (e.g., busy periods at the ASPSP)
The PISP must ensure that the Initiation and Risk sections of the domestic-payment match the corresponding Initiation and Risk sections of the domestic-payment-consent resource. If the two do not match, the ASPSP must not process the request and must respond with a 400 (Bad Request)
...