PIX
Payout with Pix
Security
For payout we implement an additional layer of security above the use of connection credentials, where we have an IP whitelist.
This whitelist contains the IP addresses authorized to initiate payouts. To carry out transactions in production, the client must previously provide this list of IP addresses that will be used to request payouts.
Payout
Merchants can transfer money to their collaborators using the payout service with Pix as the payment method.
Status
Status | Reason | Description |
---|---|---|
Opened | The order was created but not yet published in the bank. | |
Published | The order was published and is now awaiting confirmation. | |
Transferred | The bank confirmed the transaction. The order finished successfully. | |
Failed | Rejected | Something went wrong the payout order failed for rejected problems. |
Failed | ConnectionRefused | Something went wrong the payout order failed for communication problems. |
When the order status changes a webhook notification will be sent.
Testing environment
In order to test all scenarios in a testing environment, you can use the order payment_key to force the order status in the create payout response. For example, if the order payment_key is "mock_error_chave" the order status will be "Published", and after a couple of minutes, it will change to "Failed". In the table below you can find other options.
Payment_key | Response status | Status change |
---|---|---|
[email protected] | Opened | Published --> Failed |
[email protected] | Opened | Published --> Transferred |
[email protected] | Published | Failed |
Any other [email protected] | Published | Transferred |
When the order status changes a webhook notification will be sent.
Amount | Response status | Status change |
---|---|---|
1 - 1000 | Opened | Published --> Failed |
1001 - 2000 | Opened | Published --> Transferred |
2001 - 3000 | Published | Failed |
Amount > 3000 | Published | Transferred |
Updated about 1 month ago