| Table of Contents | ||||
|---|---|---|---|---|
|
the 1. Version Control
Version | Date | Description of Changes |
Bahrain OBF v1.0.0 | 25th Aug 2020 | Initial Release |
...
Once the domestic-payment-consent consents has been authorised by the Useruser/Customercustomer, the PISP can proceed to submitting submit the domestic-payment for processing:
This is done by making a POST request to the domestic-payments payment endpoint
This request is an instruction to the ASPSP to begin the single domestic 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)
...
The data dictionary section gives the detail on the payload content for the Domestic Payment API flows
...
ConsentId
The full Initiation and Risk objects from the domestic-payment-consent request
The Initiation and Risk sections The Initiation and Risk sections of the domestic-payment request must match the Initiation and Risk sections request must match the Initiation and Risk sections of the corresponding domestic-payment-consent request.
...
Name | Occurrence | XPath | Definition | Class/ Datatype | Codes | Pattern |
OBWriteDomesticPaymentRequest |
| OBWriteDomesticPaymentRequest |
| OBWriteDomesticPaymentRequest |
|
|
Data | 1..1 | OBWriteDomesticPaymentRequest/Data |
| OBWriteDomesticPaymentRequest/Data |
|
|
ConsentId | 1..1 | OBWriteDomesticPaymentRequest/Data/ConsentId | Unique identification as assigned by the ASPSP to uniquely identify the consent resource | String |
|
|
Initiation | 1..1 | OBWriteDomesticPaymentRequest/Data/Initiation | The Initiation payload is sent by the initiating party to the ASPSP. It is used to request movement of funds from the debtor account to a creditor for a single domestic payment | OBDomesticPaymentInitiation |
|
|
Risk | 1..1 | OBWriteDomesticPaymentRequest/Risk | The Risk section is sent by the initiating party to the ASPSP. It is used to specify additional details for risk scoring for Payments | OBRisk |
|
|
PaymentContextCode | 0..1 | OBWriteDomesticPaymentRequest/Risk/PaymentContextCode | This field specifies the payment context
| String | Enum:
|
|
MerchantCategoryCode | 0..1 | OBWriteDomesticPaymentRequest/Risk/MerchantCategoryCode | Category code conform to ISO 18245, related to the type of services or goods the merchant provides for the transaction | String |
|
|
MerchantCustomerIdentification | 0..1 | OBWriteDomesticPaymentRequest/Risk/MerchantCustomerIdentification | The unique customer identifier of the Useruser/Customer customer with the merchant
| String |
|
|
DeliveryAddress | 0..1 | OBWriteDomesticPaymentRequest/Risk/DeliveryAddress | Information that locates and identifies a specific address, as defined by postal services or in free format text It will contain AddressLine, StreetName, BuildingNumber, PostCode, TownName, CountrySubDivision, Country | OBWriteDomesticPaymentRequest/Risk/DeliveryAddress |
|
|
...
DomesticPaymentId
ConsentId
CreationDateTime the domestic-payment resource was created
Status and StatusUpdateDateTime of the domestic-payment resource
ExpectedExecutionDateTime for the domestic-payment resource
ExpectedSettlementDateTime for the domestic-payment resource
Refund account details, if requested by PISP as part of the domestic-payment-consents resource
Charges array for the breakdown of applicable ASPSP charges
The Initiation object from the domestic-payment-consentconsents
An ASPSP should conditionally provide Debtor/Name in the Payment Order Response, even when the Payer did not provide the Debtor Account via PISP
...