Skip to main content

​
Frequent answers and questions

CREDITED is the final status. The difference between PAID and CREDITED is that CREDITED represents when the value is available for withdrawal.
PAID is the final status.
The transactions will change status automatically, this should take up to 5 minutes to complete.To simulate different scenarios and test specific statuses, use the test scenarios available:
  • Credit Card: See Test Cards for documents that trigger different payment statuses
  • Sandbox Environment: Use to test without affecting production
Yes, transactions go through multiple intermediate statuses before reaching their final state. The time to reach the final status varies depending on the payment method and processing conditions.For detailed information about all possible statuses and their flows:Note: When you create a transaction, the first status won’t send a webhook signal. Webhooks are sent only after status changes occur.
A Brazilian citizen with a bank account can register Pix keys using a CPF/CNPJ number, mobile number, e-mail address, or a random key.However, merchant accounts at WE currently support only the random Pix key for receiving funds.
You can generate your own API key directly in the dashboard. Check the instructions here:How to create an API keyFor additional assistance, contact the Integration Team at [email protected].
  • Sandbox: Testing environment where you can test integrations without processing real transactions
  • Production: Live environment where real payments are processed
Each environment has its own API keys and URLs.
Webhooks include a signature in the request header. Use SHA-256 to hash the concatenated string and compare it with the signature header. See the Webhook Signature documentation for detailed examples.
WEPayments supports:
  • PIX: Instant payments
  • Bank Transfer: TED/DOC transfers
  • Credit/Debit Cards: Major card brands
  • Boleto: Brazilian bank slip
PIX payments are processed instantly. The status change should occur within seconds to a few minutes.
  • Payin: Can be canceled before payment is completed
  • Payout: Cancellation depends on the payment status. Contact support for assistance.
At WEpayments, you will find two distinct KYC contexts:KYC for account onboardingWhen WEpayments is responsible for onboarding your company’s account, we may request documents to complete the due-diligence process and activate your account.KYC for transaction usersIn some cases, WEpayments must collect or validate information about your users — such as payout beneficiaries or payin payers. Specific documentation may be required to process these transactions in compliance with regulatory and risk policies.For more details, please refer to the full KYC documentation.
If the CPF doesn’t match the account holder, the transaction is rejected with error codes:
  • RESTRICTION_PAYER_DIVERGENCE (for deposits)
  • BENEFICIARY_DIVERGENT (for withdrawals)
See CPF Mismatch for more details.
Use the Get Balance endpoint to retrieve your current account balance.
Use the List Institutions endpoint to get all supported banks.
This error means your API key is invalid or missing. Check that:
  • You’re using the correct API key for the environment (Sandbox/Production)
  • The API key is included in the Authorization header as a Bearer token
  • The API key hasn’t been revoked or expired
If you need to create or regenerate your API key, follow the instructions: How to create an API key
If your endpoint doesn’t respond with a 200 status code, WEPayments will retry:
  • 1st retry: After 1 minute
  • 2nd retry: After 5 minutes
  • 3rd retry: After 30 minutes
  • 4th retry: After 2 hours
  • 5th retry: After 6 hours
After 5 failed attempts, you’ll receive an email notification.
To move your integration to production, follow the steps below:
  1. Complete all testing in the Sandbox environment.
  2. Notify your onboarding contact that the homologation phase has been completed.
  3. Our team will review and confirm your production access approval.
  4. Once approved, collect your production API keys and provide your production IP addresses for whitelisting.
  5. Configure your webhooks using the production endpoints.
After completing these steps, your environment will be ready to go live.For more details, see the Going to Production guide.
Visit our Status Page to check the current status of our APIs and services.
24/7 Support Team: Our Support, Performance & CX team is available for operational and technical assistance.Help Center: Access articles on panel usage, transactions, payments, withdrawals, reports, and more.

​
Still have questions?

If you couldn’t find the answer you’re looking for, please contact our support team:

Integration Team

For API and integration questions

General Support

For general inquiries and assistance

Status Page

Check API status and uptime

Dashboard

Access your account dashboard