Issues

  • PIS instant payment

    Hello. We would like to know 3 things regarding PIS instant payment: 1. Do you support settlement in instant payment if receiving bank supports instant payment 2. Is in your production PIS enviroment DebtorIban mandatory? If yes will this change? 3. Do we receive both DebtorName and IBAN from your get.paymentID endpoint in production? TY Maurice Koel

    Status: Proposed | Reported by Hidden Thu, 22 Dec 2022 08:49:24 GMT

  • Digest incorrect

    We have an issue with de post Create Consent. We followed this documentation and also from the Berlin group, but to no avail. We keep getting the error “{"code":"SIGNATURE_INVALID","type":https://berlingroup.com/error-codes/SIGNATURE_INVALID,"title":"Digest incorrect","statusCode":401}”. We tried: - using the example in the Berlin Group documentation - using the example giving in this documentation - using our production certificates - using an empty body - remove everything but the digest and subscription-key - adjusting signature - etc.. No matter what, we keep getting the same error. I can supply the request. Can we get some help with this?

    Status: Proposed | Reported by Hidden Tue, 27 Sep 2022 09:23:09 GMT

  • Get payment information request requires Signature and Digest headers

    Hello, We have some troubles with retrieving payment and payment status. According to docs the only required header is Ocp-Apim-Subscription-Key and no body is expected. Following request results with error "code":"CERTIFICATE_MISSING" Request: Url: GET https://api-xs2a-sandbox.vanlanschot.com/xs2a/pis/v1/payments/sepa-credit-transfers/77835765-11df-4ee2-9780-7123dbd4034c/status Headers: [Ocp-Apim-Subscription-Key:"XXX"] Body: null Response: {"code":"CERTIFICATE_MISSING","type":"https://berlingroup.com/error-codes/CERTIFICATE_MISSING","title":"Missing in: QSEAL","statusCode":401} After adding qseal certificate to the request and creating Signature, we are getting {"code":"SIGNATURE_INVALID","type":"https://berlingroup.com/error-codes/SIGNATURE_INVALID","title":"Digest incorrect","statusCode":401} Calculating Digest is not possible as there's no body. What extra headers are required for "Get payment information request" and "Get payment status request"? What headers should be signed for get requests without body? Thanks for the support.

    Status: Proposed | Reported by Hidden Wed, 08 Dec 2021 12:44:11 GMT

  • [TeamPSD2] [Van Lanschot ] [FVLBNLXX] Facing issue while calling Production data APIs

    Hi, Thanks for your email. Due to Brexit, our earlier eIDAS certificates got expired on 31st Dec 2020. However, we had reached an agreement with the "fino run GmbH" to use their production certificate Please find the supporting pdf attached with this mail and also find attached a full Certificate chain (certificate, intermediate certificate(s), root certificate) zip file. Moving forward as stated in the previous email our psd2 subscription has been disabled because of Brexit. So do we need to apply for a new subscription key for using it with our new "fino run GmbH" production certificate or based on the document shared current subscription key ( f686985b97314382b58acc3c3164939e ) can be enabled?. Please advise and let us know if any further information is required from our end. Looking forward to hearing from you Thanks Pragnesh Gandhi

    Status: Proposed | Reported by Hidden Mon, 03 May 2021 18:21:25 GMT

  • [TeamPSD2] [Van Lanschot ] [FVLBNLXX] Facing issue while calling Bulk Payment APIs in Sandbox enviroment.

    Hi, We "Pelican Payment Services Ltd" are licensed TPP. We have successfully integrated with Van Lanschot sandbox AIS and PIS APIs. However, we try to consume Bulk payment API and getting the status code as "415". We use the "content-type" value as "application/json". PFA BulkPaymentAPI.txt complete request-response for your reference. Could you please help us to identify the issue in the Bulk payment API? Looking Forward to hearing from you. Let us know if any information is required from our end. Thanks and Best Regards

    Status: Proposed | Reported by Hidden Mon, 22 Mar 2021 12:52:17 GMT

  • Questions for the mandatory fields, PSD2 test data and Authorization url missing information

    Dears, we have tried to contact you via email couple of times, but without results. If it is possible, can you please provide us informations and Guidelines on the following questions: 1. Can you please clarify what should be the mandatory query values for the authorization url ? For example what should be scope value for both PIS and AIS? We are not able to authorize neither the payment or the consent. There is Authorization documentation missing and we constantly receiving an error after we tried to log in . 2. We would like to know if you provide some test data like ibans user name and password for the authorization part, etc. 3. We are not able to log in when we are using “account1’” or “account2” – please look at the attached screenshots. 4. About the "Ocp-Apim-Subscription-Key" header - We would need to know if it also required for production? Thanks in advance!

    Status: Proposed | Reported by Hidden Wed, 14 Oct 2020 06:03:17 GMT

  • Invalid Signature

    Greetings, I'm currently having problems when making a /consents request, receiving an error, stating that the signature is invalid. Could you check the attached request log and tell what is wrong with the signature? Kind regards Eugen Mocan

    Status: Proposed | Reported by Hidden Fri, 18 Sep 2020 11:58:54 GMT

  • Test certificates

    Dear support, Can you tell as if you provide some test certificate that we can use in order to test your sandbox APIs. Thanks!

    Status: Proposed | Reported by Hidden Tue, 11 Aug 2020 12:33:28 GMT

  • Constant 500 Internal Server Error

    Dear support, Please see the attached file with logs from Postman request that we are trying to perform (POST Payment/ POST Token). We are receiving 500 Internal Server Error. What seems to be the problem here? Can you also please describe the correct flows for AIS and PIS in order to complete both of them , as we don't find any Authorization ednpoint (if we need one actualy) for example Thanks!

    Status: Proposed | Reported by Hidden Thu, 06 Aug 2020 08:41:21 GMT

  • Query Related to "Corporate" and "Retail" Customer Type

    Hi, We are licensed TPP Pelican Payment Services Ltd from UK London with FCA registration number as 791330. We have successfully integrated with sandbox environment APIs provided by the bank - " Van Lanschot, Netherland ". We have a query and would like to have your valuable input for the same. It would be of great help if you can help us know how can we outreach to "Corporate" and "Retail" customers of your bank through PSD2 APIs. Do the different customer types namely  "Corporate" and "Retail" have different sandbox environment APIs ? or all the different customer types can be reached through the same API exposed at the developer portal i.e "https://xs2a-sandbox.vanlanschot.com/ ". Kindly guide us for the same and help us outreach to most of your customers. Do let us known if any further information is required from our end. Thanks in advance.

    Status: Proposed | Reported by Hidden Thu, 04 Jun 2020 14:44:25 GMT

You're not signed in. Please sign-in to report an issue or post a comment.