Implementation Guide: Advanced Payment Solutions (Cashplus Bank)

This page has been created and maintained by the relevant ASPSP, and OBIE takes no liability for the completeness nor accuracy of this data.

Note to ASPSP: Please indicate which brands this applies to and/or duplicate this page per brand if relevant.


ASPSPAdvanced Payment Solutions
Brand

Cashplus Bank

Date
Developer portal (s)https://developer.cashplus.com/

Announcements

Improvement
Delivery date

v 3.1 Dynamic registration, identity/authentication and Account Information endpoints available for testing in Sandbox

 
v 3.1.2 Account information endpoints available for testing in Production28/Aug/19
v 3.1.2 Payment endpoints available for testing in Production13/Sept/19
v 3.1.2 Funds Confirmation endpoints available for testing in Production13/March/20

On-boarding

Supports dynamic client registration (Y/N)Y
Instructions for manual onboardingn/a
OIDC .well-known endpoint

Sandbox:    https://sandbox.identity.ob.cashplus.com/.well-known/openid-configuration

Production: https://identity.ob.cashplus.com/.well-known/openid-configuration

Notes on testing
Other on-boarding notes

To on-board developers must:

1. Register/Enrol with Open Banking

2. Submit Software Statement Assertion to Client Registration endpoint

Sandbox: https://sandbox.matls.identity.ob.cashplus.com/tpp/register

Production: https://matls.identity.ob.cashplus.com/tpp/register


When migrating from OB legacy certificates to the OBWAC and OBSEAL, new client must be created.
Documentation URL


https://developer.cashplus.com/

AISP:  https://developer.cashplus.com/docs/swagger_accounts.json

PISP:  https://developer.cashplus.com/docs/swagger_payments.json



Sandbox PSU Accounts

Username
Password

JohnSmith

4eQY?$D%zm

Sandbox SCA authentication codes

Valid Code

12345678

Account Information API

Swagger version

Account and Transactions API (v3.1.2)

https://developer.cashplus.com/docs/swagger_accounts.json
Base URI
General variances to specification offline_access required in JWT request object scopes for refresh_token to be issued in authorisation flow
Non-functional limitations
RefAreaFieldAvailable (Y/N)Exception/Notes (inc details on classification codes, field limits, and field formats)
1Account Access Consents

POST  /account-access-consents

GET /account-access-consents/{ConsentId}

DELETE /account-access-consents/{ConsentId}

Y

Permissions :

ReadAccountsBasic
ReadAccountsDetail
ReadBalances
ReadBeneficiariesBasic
ReadBeneficiariesDetail
ReadDirectDebits
ReadScheduledPaymentsBasic
ReadScheduledPaymentsDetail
ReadStandingOrdersBasic
ReadStandingOrdersDetail
ReadStatementsBasic
ReadStatementsDetail
ReadTransactionsBasic
ReadTransactionsCredits
ReadTransactionsDebits
ReadTransactionsDetail

2Accounts

GET /accounts

GET /accounts/{AccountId}

Y
3Balances

GET /balances

GET /accounts/{AccountId}/balances

Y
4Beneficiaries

GET /beneficiaries

GET /accounts/{AccountId}/beneficiaries


5Direct Debits

GET /direct-debits

GET /accounts/{AccountId}/direct-debits


6Offers

GET /offers

GET /accounts/{AccountId}/offers

N
7Party

GET /party

GET /accounts/{AccountId}/party

N
8Products

GET /products

GET accounts/{AccountId}/product

N
9Scheduled Payments

GET /scheduled-payments

GET /accounts/{AccountId}/scheduled-payments


10Standing Orders

GET /standing-orders

GET /accounts/{AccountId}/standing-orders


11Statements

GET /accounts/{AccountId}/statements/{StatementId}/file


12Transactions

GET /transactions

GET /accounts/{AccountId}/transactions

GET /accounts/{AccountId}/statements/{StatementId}/transactions

YWe only provide 18 months of transaction history 


Payment Initiation API


AreaFieldAvailable (Y/N)Exception/Notes (inc details on classification codes, field limits, and field formats)
1Domestic Payment Consent

POST  /domestic-payment-consents

GET /domestic-payment-consents/{ConsentId}

DELETE /domestic-payment-consents/{ConsentId}

GET/domestic-payment-consents/{ConsentId}/funds-confirmation

Y

Remittance information object is mandatory. At least one of the fields reference or unstructured must be provided.

2Domestic Payment

POST/domestic-payments

GET/domestic-payments/{DomesticPaymentId}

YRemittance information object is mandatory. At least one of the fields reference or unstructured must be provided.
3Domestic Scheduled Payment Consent

POST  /domestic-scheduled-payment-consent

GET /domestic-scheduled-payment-consent/{ConsentId}

Y



Remittance information object is mandatory. At least one of the fields reference or unstructured must be provided.
4Domestic Scheduled Payment

POST  /domestic-scheduled-payment

GET /domestic-scheduled-payment/{DomesticScheduledPaymentId}

YRemittance information object is mandatory. At least one of the fields reference or unstructured must be provided.
5Domestic Standing Order Consent

POST  /domestic-standing-order-consents

GET /domestic-standing-order-consents/{ConsentId}

Y
  1. Supported frequency: 
IntrvlWkDay:01
IntrvlWkDay:02
IntrvlWkDay:04
IntrvlMnthDay:01
IntrvlMnthDay:02
IntrvlMnthDay:03
IntrvlMnthDay:06
IntrvlMnthDay:12
IntrvlMnthDay:24
2. ReccuringPaymentAmount and FinalPaymentAmount must be the same as FirstPaymentAmount
3. RecurringPaymentDateTime must be the same as FirstPaymentDateTime
4. FinalPaymentDateTime is the date until the SO is valid
6Domestic Standing Order 

POST  /domestic-standing-order

GET /domestic-standing-order/{DomesticStandingOrderId}

Y
  1. Supported frequency: 
IntrvlWkDay:01
IntrvlWkDay:02
IntrvlWkDay:04
IntrvlMnthDay:01
IntrvlMnthDay:02
IntrvlMnthDay:03
IntrvlMnthDay:06
IntrvlMnthDay:12
IntrvlMnthDay:24
2. ReccuringPaymentAmount and FinalPaymentAmount must be the same as FirstPaymentAmount
3. RecurringPaymentDateTime must be the same as FirstPaymentDateTime
4. FinalPaymentDateTime is the date until the SO is valid

Confirmation of Funds API

Swagger version

Confirmation of Funds API (v3.1.2)

Base URI

https://sandbox.matls​​​​​​​.api.ob.cashplus.com​​​​​​​/open-banking/v3.1/cbpii

General variances to specification
Non-functional limitations

Area
Field
Available (Y/N)
Exception/Notes (inc details on classification codes, field limits, and field formats)
1Funds Confirmation Consent

POST /funds-confirmation-consents

GET /funds-confirmation-consents/{ConsentId}

DELETE /funds-confirmation-consents/{ConsentId}

Y
2Funds Confirmation 

POST /funds-confirmations


Y

Open Data API

Swagger version
Base URI
General variances to specification 
Non-functional limitations
RefAreaFieldAvailable (Y/N)Exception/Notes (inc details on classification codes, field limits, and field formats)