@hook-sdk/template 0.18.0 → 0.18.1

package/dist/index.d.cts

@@ -723,7 +723,21 @@ declare function shouldBlockInstall(state: InstallState, now?: number): boolean;
  */
 declare function shouldShowPermanentOption(state: InstallState): boolean;
 
-declare function asaasErrorMessage(code: string): string;
+/**
+ * Map Asaas error → PT-BR user-facing message.
+ *
+ * Two inputs because backend folds Asaas's specific error code into a
+ * compound code (`payments.capture_card.tokenize_failed:invalid_holderInfo`)
+ * and only the *description* string ("O CEP informado é inválido.")
+ * distinguishes between sub-cases of `invalid_holderInfo` (CEP, phone, name).
+ *
+ * Asaas keeps a snapshot of Correios CEPs that lags real registrations by
+ * months — CEPs of recently-cadastrated streets (ex: bairros novos) get
+ * rejected even though they're valid in ViaCEP/BrasilAPI. We don't suggest
+ * a fictitious CEP (would mess up nota fiscal/comms); we explain the issue
+ * is on the processor's side and ask user to try a nearby street's CEP.
+ */
+declare function asaasErrorMessage(code: string, description?: string): string;
 
 type RouteBoundaryProps = {
     children: ReactNode;

package/dist/index.d.ts

@@ -723,7 +723,21 @@ declare function shouldBlockInstall(state: InstallState, now?: number): boolean;
  */
 declare function shouldShowPermanentOption(state: InstallState): boolean;
 
-declare function asaasErrorMessage(code: string): string;
+/**
+ * Map Asaas error → PT-BR user-facing message.
+ *
+ * Two inputs because backend folds Asaas's specific error code into a
+ * compound code (`payments.capture_card.tokenize_failed:invalid_holderInfo`)
+ * and only the *description* string ("O CEP informado é inválido.")
+ * distinguishes between sub-cases of `invalid_holderInfo` (CEP, phone, name).
+ *
+ * Asaas keeps a snapshot of Correios CEPs that lags real registrations by
+ * months — CEPs of recently-cadastrated streets (ex: bairros novos) get
+ * rejected even though they're valid in ViaCEP/BrasilAPI. We don't suggest
+ * a fictitious CEP (would mess up nota fiscal/comms); we explain the issue
+ * is on the processor's side and ask user to try a nearby street's CEP.
+ */
+declare function asaasErrorMessage(code: string, description?: string): string;
 
 type RouteBoundaryProps = {
     children: ReactNode;

package/dist/index.js

@@ -196,7 +196,16 @@ var MAP = {
   pix_expired: "QR Code do PIX expirou. Gere um novo.",
   pix_not_paid_yet: "PIX ainda n\xE3o foi pago. Aguardando confirma\xE7\xE3o."
 };
-function asaasErrorMessage(code) {
+function asaasErrorMessage(code, description) {
+  if (description) {
+    const lower = description.toLowerCase();
+    if (lower.includes("cep")) {
+      return "Nosso processador de pagamentos n\xE3o reconheceu esse CEP \u2014 a base deles pode estar desatualizada. Tente outro CEP.";
+    }
+    if (lower.includes("telefone") || lower.includes("contato com ddd")) {
+      return "Telefone inv\xE1lido. Confira o n\xFAmero com DDD e tente novamente.";
+    }
+  }
   return MAP[code] ?? "Ocorreu um erro inesperado. Tente novamente em instantes.";
 }
 
@@ -325,7 +334,9 @@ function usePaywallState() {
     (code, fallbackMessage) => ({
       code,
       message: fallbackMessage,
-      userMessage: useDefaultMessages ? asaasErrorMessage(code) : fallbackMessage
+      // fallbackMessage carries Asaas's PT-BR description ("O CEP informado é inválido.")
+      // that distinguishes invalid_holderInfo sub-cases (CEP vs phone vs name).
+      userMessage: useDefaultMessages ? asaasErrorMessage(code, fallbackMessage) : fallbackMessage
     }),
     [useDefaultMessages]
   );