@riocrypto/common-server 1.0.2834 → 1.0.2836

package/build/helpers/get-processor.js

@@ -2,6 +2,10 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.getProcessor = void 0;
 const common_1 = require("@riocrypto/common");
+// Alfin only takes effect in Test/Local. In every other environment we never
+// route to Alfin (regardless of user attributes or active processors), so the
+// service can be deployed before Alfin is actually enabled.
+const isAlfinEnabled = () => [common_1.RioEnv.Test, common_1.RioEnv.Local].includes(process.env.RIO_ENV);
 const getProcessor = ({ country, fiat, user, activeProcessors, side, isBinanceRFQ, }) => {
     var _a, _b, _c, _d, _e, _f;
     if (isBinanceRFQ === true) {
@@ -18,11 +22,13 @@ const getProcessor = ({ country, fiat, user, activeProcessors, side, isBinanceRF
     else if (fiat === common_1.Fiat.PEN) {
         if (country === common_1.Country.Peru) {
             if (side === common_1.Side.Buy &&
+                isAlfinEnabled() &&
                 ((_a = user.attributes) === null || _a === void 0 ? void 0 : _a.includes(common_1.UserAttribute.UseAlfinForPENDeposits)) &&
                 activeProcessors.includes(common_1.Processor.Alfin)) {
                 return common_1.Processor.Alfin;
             }
             if (side === common_1.Side.Sell &&
+                isAlfinEnabled() &&
                 ((_b = user.attributes) === null || _b === void 0 ? void 0 : _b.includes(common_1.UserAttribute.UseAlfinForPENWithdrawals)) &&
                 activeProcessors.includes(common_1.Processor.Alfin)) {
                 return common_1.Processor.Alfin;
@@ -71,11 +77,13 @@ const getProcessor = ({ country, fiat, user, activeProcessors, side, isBinanceRF
         }
         else if (country === common_1.Country.Peru) {
             if (side === common_1.Side.Buy &&
+                isAlfinEnabled() &&
                 ((_e = user.attributes) === null || _e === void 0 ? void 0 : _e.includes(common_1.UserAttribute.UseAlfinForUSDDeposits)) &&
                 activeProcessors.includes(common_1.Processor.Alfin)) {
                 return common_1.Processor.Alfin;
             }
             if (side === common_1.Side.Sell &&
+                isAlfinEnabled() &&
                 ((_f = user.attributes) === null || _f === void 0 ? void 0 : _f.includes(common_1.UserAttribute.UseAlfinForUSDWithdrawals)) &&
                 activeProcessors.includes(common_1.Processor.Alfin)) {
                 return common_1.Processor.Alfin;

package/build/models/bank-account-verification.d.ts

@@ -6,7 +6,7 @@ interface BankAccountVerificationAttrs {
     bankAccountId: string;
     status: BankAccountVerificationStatus;
     amount: number;
-    provider?: Processor.SPEI_STP | Processor.SPEI_NVIO;
+    provider?: Processor.SPEI_STP | Processor.SPEI_NVIO | Processor.Alfin;
     providerWithdrawalId?: string;
     SPEITrackingNumber?: string;
     CEPLink?: string;
@@ -21,7 +21,7 @@ interface BankAccountVerificationDoc extends Document {
     bankAccountId: string;
     status: BankAccountVerificationStatus;
     amount: number;
-    provider?: Processor.SPEI_STP | Processor.SPEI_NVIO;
+    provider?: Processor.SPEI_STP | Processor.SPEI_NVIO | Processor.Alfin;
     providerWithdrawalId?: string;
     SPEITrackingNumber?: string;
     CEPLink?: string;

package/build/models/compliance-bot-rule-result.d.ts

@@ -13,6 +13,7 @@ interface ComplianceRuleResultAttrs {
     outcome?: ComplianceRuleOutcome;
     tag?: string;
     renderMarkdown?: boolean;
+    displayOrder?: number;
 }
 interface ComplianceRuleResultDoc extends mongoose.Document {
     id: string;
@@ -27,6 +28,7 @@ interface ComplianceRuleResultDoc extends mongoose.Document {
     outcome?: ComplianceRuleOutcome;
     tag?: string;
     renderMarkdown?: boolean;
+    displayOrder?: number;
 }
 interface ComplianceRuleResultModel extends mongoose.Model<ComplianceRuleResultDoc> {
     build(attrs: ComplianceRuleResultAttrs): HydratedDocument<ComplianceRuleResultDoc>;

package/build/models/compliance-bot-rule-result.js

@@ -60,6 +60,13 @@ const buildComplianceRuleResult = (mongoose) => {
             required: false,
             default: false,
         },
+        // Snapshot of the parent rule's displayOrder at run time so
+        // the PDF report orders rows within a tag group correctly
+        // even after the rule is reordered or deleted.
+        displayOrder: {
+            type: Number,
+            required: false,
+        },
     }, {
         toJSON: {
             transform(doc, ret) {

package/build/models/compliance-bot-rule.d.ts

@@ -9,6 +9,7 @@ interface ComplianceRuleAttrs {
     ruleSetId?: string;
     tag?: string;
     renderMarkdown?: boolean;
+    displayOrder?: number;
 }
 interface ComplianceRuleDoc extends mongoose.Document {
     id: string;
@@ -20,6 +21,7 @@ interface ComplianceRuleDoc extends mongoose.Document {
     ruleSetId?: string;
     tag?: string;
     renderMarkdown?: boolean;
+    displayOrder?: number;
 }
 interface ComplianceRuleModel extends mongoose.Model<ComplianceRuleDoc> {
     build(attrs: ComplianceRuleAttrs): HydratedDocument<ComplianceRuleDoc>;

package/build/models/compliance-bot-rule.js

@@ -55,6 +55,15 @@ const buildComplianceRule = (mongoose) => {
             required: false,
             default: false,
         },
+        // Presentational sort key within the rule's
+        // (ruleSetId, stepType) section. Assigned by drag/drop
+        // reordering in the Dexter rules tree; orders rules in the
+        // GUI and the PDF report. Does not affect engine execution
+        // order. Optional/absent for legacy rules (sort last).
+        displayOrder: {
+            type: Number,
+            required: false,
+        },
     }, {
         toJSON: {
             transform(doc, ret) {
@@ -70,6 +79,9 @@ const buildComplianceRule = (mongoose) => {
     // the "tag" field in the rule editor: distinct(tag) scoped to a
     // ruleSet, including only rules that actually carry a tag.
     ComplianceRuleSchema.index({ ruleSetId: 1, tag: 1 });
+    // Supports the per-step-type ordered fetch used by the rules tree
+    // and the reorder write path (rules of a set+step in display order).
+    ComplianceRuleSchema.index({ ruleSetId: 1, stepType: 1, displayOrder: 1 });
     ComplianceRuleSchema.statics.build = (attrs) => {
         return new ComplianceRule(attrs);
     };

package/build/models/compliance-rule-set.d.ts

@@ -5,6 +5,7 @@ interface ComplianceRuleSetAttrs {
     name: string;
     description?: string;
     isDefault: boolean;
+    tagOrder?: string[];
     createdAt: Date;
     updatedAt: Date;
 }
@@ -15,6 +16,7 @@ interface ComplianceRuleSetDoc extends mongoose.Document {
     name: string;
     description?: string;
     isDefault: boolean;
+    tagOrder?: string[];
     createdAt: Date;
     updatedAt: Date;
 }

package/build/models/compliance-rule-set.js

@@ -27,6 +27,14 @@ const buildComplianceRuleSet = (mongoose) => {
             required: true,
             default: false,
         },
+        // Ordered list of tag labels controlling tag-group sequence
+        // in the PDF report. Tags absent from this list render after
+        // (alphabetically); the untagged bucket is always last.
+        tagOrder: {
+            type: [String],
+            required: false,
+            default: [],
+        },
         createdAt: {
             type: Date,
             required: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@riocrypto/common-server",
-  "version": "1.0.2834",
+  "version": "1.0.2836",
   "description": "",
   "main": "./build/index.js",
   "types": "./build/index.d.ts",
@@ -28,7 +28,7 @@
     "@google-cloud/secret-manager": "^5.6.0",
     "@google-cloud/storage": "^7.19.0",
     "@hyperdx/node-opentelemetry": "^0.10.3",
-    "@riocrypto/common": "1.0.2633",
+    "@riocrypto/common": "1.0.2637",
     "@slack/web-api": "^7.15.0",
     "@types/express": "^4.17.25",
     "axios": "1.16.0",