Skip to content
This repository was archived by the owner on Feb 3, 2023. It is now read-only.

Conversation

@mmaica
Copy link

@mmaica mmaica commented Feb 21, 2022

https://bitsomx.atlassian.net/browse/RAILSBR-379

Relates to this document: https://bitsomx.atlassian.net/wiki/spaces/Rails/pages/3263234056/Pix+third+party+withdrawals

  • In order to perform a withdrawal to a PIX key, first we have to get the bank account details related to that PIX key; this is done though BR banking integration and goes to the central bank;
  • Bank account details contain sensitive personal information;
  • We (as a company) are subject to throttling/temporary blocks as this mechanism may be abused to obtain sensitive personal information;
  • This throttling/temporary block that may be applied on us is based on token bucket concept;
  • We are going to temporarily block our users individually when they take us to scenarios where we spend tokens; this is what this new error is about

@mmaica mmaica changed the title Adding new error code to errors related to an account because a user may be blocked to perform BRL PIX withdrawals if they suffer too many PIX key query attempts. Adding new error code to errors related to an account because a user may be blocked to perform BRL PIX withdrawals if they suffer too many PIX key query failed attempts. Feb 21, 2022
@mmaica mmaica force-pushed the feature/RAILSBR-379 branch 2 times, most recently from ff625eb to 8cf6ca5 Compare February 21, 2022 19:22
…may be blocked to perform BRL PIX withdrawals if they suffer too many PIX key query failed attempts.
@mmaica mmaica force-pushed the feature/RAILSBR-379 branch from 8cf6ca5 to ac066ce Compare February 21, 2022 19:26
@axe-bitso
Copy link
Contributor

Just one question: Is this going to be used by the frontend or would anyone interacting with the site through the API could get that error?

@mmaica
Copy link
Author

mmaica commented Feb 22, 2022

Just one question: Is this going to be used by the frontend or would anyone interacting with the site through the API could get that error?

Front ends are using our error messages (coming from message bundles in withdrawal-* services) as pass-through, i.e. they are not using the error code to map to an error message. This API is accessible through public API (withdrawals) though as far as I understand, and they may suffer this error too.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants