Sign Up for Developer Portal

To create an account, please fill out the form below.

The form below is filled incorrectly. Please check for mistakes.
Access Denied: Possible Bot Activity
Already have an account?

Sign In to Developer Portal

To sign in, fill out the form below.

The form below is filled incorrectly. Please check for mistakes.
Forgot your password?
Reset password here

Password reminder

To get a password reminder type in your email address bellow. The message will be sent to the following email.

Registration successful

Checkmark

Confirmation email

Confirmation email was sent to .
Please, check your inbox.

Continue

Resetting successful

Checkmark

Confirmation email

Confirmation email was sent to .
Please, check your inbox.

Continue

Šiaulių bankas' PSD2 API: SEPA Instant Payment Reject Reason in GET Payment Status Endpoint

Dear Third-Party Provider, 

We hope this message finds you well. 

It has come to our attention that on some occasions, when a SEPA Instant transaction is rejected by the bank, your PIS software does not know the exact reason. This significantly affects the PSU journey, as they are unable to pay for goods or services. We offer the following solution: 

SEPA Instant Payment reject reason has been included in the response of GET endpoint: v3/payments/instant-sepa-credit-transfers/{paymentId}/status for a better understanding of rejected payments from the bank's side, as well as improving PIS journey: 

{"transactionStatus":"RJCT","fundsAvailable":false,"tppMessages":[{"category":"ERROR","code":"SEPA_INSTANT_NOT_POSSIBLE","text":"We recommend initiating a SEPA credit transfer"}]} 

We highly recommend reviewing the section on 'Common error messages' in our documentation or Swagger file for more details. Implementing this change can lead to a more efficient system and enhance the end-user experience by reducing the need for repeated payment attempts. 

If you have any questions or need further assistance, please do not hesitate to reach out. 

Thank you for your cooperation.

We use cookies on this site to ensure you have the best browsing experience.
Read more